A Call Detail Record (CDR) is a structured log of a phone call that includes metadata such as:

• Call direction (inbound/outbound)
• Start and end timestamps
• Call status (answered, busy, failed, canceled, etc.)
• Caller and callee numbers
• Duration (billed and total)
• Billing info
• Hangup cause and source

This data is essential for reporting, analytics, billing, tracking, and debugging.

🔍 Accessing CDRs

There are multiple ways to access CDRs depending on your use case and integration style.

🛠️ Inside Callr Actions Scenarios

✅ For Inbound Calls

When a call reaches your inbound-call branch, the CDR is available via the call.cdr object. During the call it is partial (it can even be null in the first actions): the end of call fields (ended, hangup*, duration*, billing* amounts, status) only appear once the call has ended. In the hangup branch, the CDR is complete.

- action: log@v1
  params:
    message: CDR=${{ JSON.stringify(call.cdr) }}

You can push the CDR to your backend using fetch@v3, typically from the hangup branch.

✅ For Outbound Calls (using dial@v2)

- action: dial@v2
  params:
    targets:
      - number: "+33639980042"
        timeout: 60
  result: $dial

- action: log@v1
  params:
    message: CDR=${{ JSON.stringify($dial.cdr) }}

$dial.cdr is null when the CDR of the outbound call is not ready a few seconds after the call: use $dial?.cdr in expressions.

The typical use case is to push the CDR to your platform (more examples here: Push Data to Your Platform).

- action: fetch@v3
  params:
    url: https://...
    method: POST
    headers:
      content-type: application/json
    body: |
      {
        "cdr": ${{ JSON.stringify(call.cdr) }}
      }

🌐 Webhooks (v2.call.*)

If you're using Callr Webhooks, the CDR is included in the payload of the following event types:

• v2.call.inbound.started
• v2.call.inbound.ended
• v2.call.outbound.started
• v2.call.outbound.ended

You’ll receive the same CDR structure as available in Callr Actions — including full call metadata and billing info.

📘

Tip

💡 Make sure your webhook server is ready to handle POST requests and validate incoming data.

📦 CDR Export API

For historical data or bulk exports, use the CDR export endpoint.

curl --request POST \
     --url 'https://api.callr.com/v2.0/calls/export?direction=<direction>&from=<from>&to=<to>' \
     --header 'accept: application/json' \
     --header 'x-api-key: <your-callr-api-key>'

The export is asynchronous:

1. The request returns 202 with a Task ID.
2. Follow the task with GET /v2.0/tasks/{taskid}, or subscribe to the v2.task.updated webhook.
3. When the task is done, its result gives the CSV file. The file stays available for 24 hours.

🚧

Limits

An export covers at most 31 days: split longer periods into several requests. You can run at most 5 exports per day. For real-time processing, use webhooks or fetch@v3 instead.

🧾 CDR Fields Overview