Skip to main content
GET
Retrieve a CDR by call ID
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

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
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