Skip to main content
Retrieve detailed call logs, billing data, and per-call telemetry for your account. Vobiz CDRs include caller/callee identifiers, timing, billing, hangup attribution, and quality metrics (MOS, jitter, packet loss). Use them for billing reconciliation, traffic analysis, fraud detection, and compliance reporting.
Authentication: All CDR endpoints use API key authentication. Pass X-Auth-ID and X-Auth-Token in your request headers.

Endpoints Overview

List CDRs

Returns CDRs for your account. Supports filtering by phone numbers, date range, call direction, duration, and pagination. Response includes a summary block with aggregate metrics across the filtered set.

Get Single CDR

Retrieve full detail for a specific call by its call_id. Useful when you have a call_id from a webhook callback or previous list response.
cURL

Search CDRs

Identical filters to the list endpoint, but the response also includes a filters object echoing the active filters applied. Useful when building search UIs that need to display current filter state.
cURL

Recent CDRs

Returns the most recent CDRs for your account without requiring a date range. Returns 20 records by default. Use limit to retrieve more. Note: the recent endpoint does not return pagination or summary blocks - just data.
cURL

Export as CSV

Returns CDR data as a downloadable CSV file. Supports the same filters as the list endpoint. Use the -o flag in curl to save directly to a file.
cURL
The export endpoint returns text/csv content. Do not send Accept: application/json on this request.

Query Parameters

Filter Parameters (list, search, export)

Response Structure

A successful list/search request returns:
200 OK - Response

Top-level fields

Pagination object

Summary object

CDR object - every field

hangup_source cannot distinguish a platform teardown from a participant hangup on conference legs.A leg removed by another member’s endConferenceOnExit receives no hangup attribution, so it falls through to the default and reports as NORMAL_CLEARING / 4000 / Callee - identical to the participant having hung up themselves.If you reconcile disconnections from hangup_source, correlate against ConferenceExit callbacks rather than trusting the CDR field alone. See Conference attributes.
| failure_code | string | null | Failure code if the call did not connect. | | failure_reason | string | null | Human-readable failure reason. | | bridge_uuid | string (UUID) | null | UUID of the call bridge. | | sip_call_id | string | SIP-level Call-ID header value. | | sip_user_agent | string | SIP User-Agent header value of the originating leg. | | codec | string | null | Audio codec negotiated (e.g. PCMU, PCMA, opus). | | mos | number | Mean Opinion Score (call audio quality, 1.0–5.0). | | jitter | number | Jitter in milliseconds. | | packet_loss | number | Packet loss percentage. | | network_addr | string | Network address of the call leg. | | carrier_ip | string | null | Carrier IP address. | | context | string | Internal call context (e.g. voice-api). | | region | string | Vobiz infrastructure region (e.g. ap-south-1). | | origination_region | string | Region the call originated from. | | campaign_id | string | null | Campaign ID if the call is part of a campaign. | | customer_endpoint | string | null | Customer endpoint identifier. | | trunk_id | string | null | SIP trunk ID used for this call. | | terminated_to | string | null | Termination target if forwarded. |

Hangup Causes

The table below describes common SIP/B2BUA hangup_cause values you may encounter in your call logs.

Examples

Filter by date range

Outbound calls only, minimum 10 seconds

Last 50 recent calls

Export filtered CDRs to CSV

What to do next

Diagnose a hangup_cause with an AI agent

Paste a CDR or a hangup_cause code - get a plain-English diagnosis and remediation steps.

Open in Cursor