Skip to main content
GET
List customer CDRs
← Partner API Reference Full call detail records for every voice session across your partner ecosystem. Filter by date range, direction, hangup cause, number, and more. Essential for billing reconciliation, call quality troubleshooting, and traffic monitoring.
All Partner API requests use X-Auth-ID and X-Auth-Token headers. See Authentication for details.

Overview

The CDR API gives you read access to call logs for all customers under your partner account. Three endpoints cover different scopes:
  • Customer CDRs - Filtered CDR log for one customer. Most common - use for per-customer billing and support tickets.
  • Single CDR by UUID - Deep forensic detail for one specific call by its UUID. Use for troubleshooting a specific incident.
  • All CDRs (Global) - Global traffic log across all accounts. Use for platform-wide quality monitoring and aggregate reporting.

Customer CDRs

Returns a paginated CDR log for one specific customer. All filter parameters are optional - omit all to get the most recent calls paginated by default.

Available Filters

The date filters here are start_date / end_date (CDRs), not from_date / to_date as used by the Transactions endpoint. Status values are underscored: no_answer, not no-answer.

Examples

Response

Get Specific CDR by UUID

Returns complete detail for a single call identified by its UUID. Use this when a customer reports a specific call issue - pass the call UUID from their system or from a previous CDR list query. This endpoint exposes the full call metadata, including SIP response codes and media quality indicators where available.

All CDRs (Global)

Global CDR log across all customer accounts under your partner umbrella, returned as a single paginated response. Supports all the same filter parameters as the per-customer endpoint. Use for platform-wide traffic monitoring and identifying customers with unusual call patterns.

Response shape

The list response wraps the records in a fixed envelope:
For billing, multiply each row’s billsec (billable seconds), not raw duration, by your per-minute rate - or simply read summary.total_cost, which Vobiz has already computed at the customer’s pricing tier.

Use Cases

  • Per-customer billing - Pull CDRs for a customer for the billing period. Use summary.total_cost for the period total, or sum billsec across rows if you apply your own markup.
  • Call quality troubleshooting - When a customer reports poor call quality, pull the specific CDR by UUID. Check hangup_cause, mos, jitter, and packet_loss for the root cause.
  • No-answer rate monitoring - Filter by status=no_answer over the past 7 days. High no-answer rates indicate number configuration issues or customer routing problems.
  • Fraud detection - Watch for abnormal call volumes or unusual call durations in the global CDR feed. Spikes in short-duration outbound calls can indicate robocalling abuse.

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

customer_auth_id
string
required

Query Parameters

start_date
string<date>
end_date
string<date>
call_direction
enum<string>
Available options:
inbound,
outbound
status
enum<string>
Available options:
answered,
failed,
busy,
no_answer
min_duration
integer
hangup_cause
string
Example:

"NO_ANSWER"

per_page
integer
default:20

Response

200 - application/json

Customer CDRs

account_id
string
required
count
integer
required
data
array
required
pagination
object
required
success
boolean
required
summary
object
required
account_auth_id
string
required