Skip to main content
GET
/
api
/
v1
/
Account
/
{auth_id}
/
cdr
/
{call_id}
Retrieve a CDR by call ID
curl --request GET \
  --url https://api.vobiz.ai/api/v1/Account/{auth_id}/cdr/{call_id} \
  --header 'X-Auth-ID: <api-key>' \
  --header 'X-Auth-Token: <api-key>'
{
  "data": {
    "account_id": "MA_XXXXXXXX",
    "answer_time": "2026-03-25T10:00:01Z",
    "billsec": 42,
    "bridge_uuid": "11223344-5566-7788-99aa-bbccddeeff00",
    "call_direction": "outbound",
    "caller_id_name": "John Doe",
    "caller_id_number": "+919876543210",
    "campaign_id": null,
    "carrier_ip": "10.0.0.1",
    "codec": "PCMU",
    "context": "voice-api",
    "cost": 0.45,
    "created_at": "2026-03-25T10:00:42Z",
    "currency": "INR",
    "customer_endpoint": null,
    "destination_number": "+918012345678",
    "duration": 47,
    "end_time": "2026-03-25T10:00:42Z",
    "failure_code": null,
    "failure_reason": null,
    "hangup_cause": "NORMAL_CLEARING",
    "hangup_cause_code": 4000,
    "hangup_cause_name": "Normal Hangup",
    "hangup_disposition": "send_bye",
    "hangup_source": "Caller",
    "id": 18000004,
    "jitter": 0,
    "mos": 4.5,
    "network_addr": "10.0.0.1",
    "origination_region": "mumbai",
    "packet_loss": 0,
    "progress_time": "2026-03-25T10:00:00Z",
    "region": "ap-south-1",
    "ring_time": 5,
    "sip_call_id": "11223344-5566-7788-99aa-bbccddeeff00",
    "sip_user_agent": "Vobiz",
    "start_time": "2026-03-25T10:00:00Z",
    "streaming_cost": 0,
    "terminated_to": null,
    "total_cost": 0.45,
    "trunk_id": null,
    "updated_at": "2026-03-25T10:00:42Z",
    "uuid": "aabbccdd-1234-5678-90ab-cdef12345678"
  },
  "success": true
}
Retrieve the full CDR for one completed call. Unlike the list endpoints, the response is { data, success } where data is a single object (not an array) - and there is no pagination, summary, or filters block.
Pass the call’s uuid, not the numeric id. The path parameter is named call_id, but the value it expects is the call’s uuid (the value you see in data[].uuid from a list/search response, or the CallUUID delivered to your webhooks). Feeding back the numeric data[].id returns 404.

​
Path parameters

ParameterTypeRequiredDescription
auth_idstringYesYour master account ID, e.g. MA_XXXXXXXX.
call_idstringYesThe call’s uuid, e.g. aabbccdd-1234-5678-90ab-cdef12345678.

​
Edge cases

  • Unknown or wrong-format ID: returns 404 (no data). Re-check that you passed the uuid and not the numeric id.
  • Call not yet complete: a CDR exists only after the call ends, so an in-progress call’s uuid will not resolve here. Use Live Calls for active calls.
  • Casing: Account is capitalized, cdr is lowercase.

​
Example

cURL
curl "https://api.vobiz.ai/api/v1/Account/{auth_id}/cdr/aabbccdd-1234-5678-90ab-cdef12345678" \
  -H "X-Auth-ID: {auth_id}" \
  -H "X-Auth-Token: {auth_token}"
See the CDR overview for the full field glossary and Hangup Causes to decode the hangup fields.

Authorizations

​
X-Auth-ID
string
header
required

Your Vobiz account Auth ID

​
X-Auth-Token
string
header
required

Your Vobiz account Auth Token

Path Parameters

​
auth_id
string
required

Your account Auth ID

Example:

"MA_XXXXXX"

​
call_id
string
required

The unique call ID of the completed call.

Example:

"abc123-def456-ghi789"

Response

CDR details

​
data
object
required
​
success
boolean
required