Call Detail Records (CDR)
A call detail record (CDR) is written for every call handled by the platform: who called whom, when, for how long, through which queue or conference, and how the call ended. These endpoints return the call detail records (call history) of your account, one month or one day at a time — a simple way to feed your own reporting, billing checks or CRM journaling.
The account is normally implied by your API key. If your key gives
access to several accounts, add an account parameter to select one.
List CDRs for a month or a day
GET https://api.ubity.com/cdr/<year>/<month>
GET https://api.ubity.com/cdr/<year>/<month>/<day>
| Parameter | Description |
|---|---|
| key | Your Ubity API key |
Each record contains:
| Field | Description |
|---|---|
| id | The unique id of the call |
| date | The call date, as a Unix timestamp in milliseconds |
| from_number | The calling number |
| from_ext | The calling extension (if any) |
| to_num | The called number |
| to_ext | The called extension (if any) |
| duration | The call duration, in seconds |
| queue | The queue name, when the call went through a queue |
| conf_name | The conference name, when the call was a conference |
| disposition | The call disposition (ie. 'ANSWERED', 'NO ANSWER', ...) |
| type | The call type (see below) |
The type field is one of: internal, local, long-distance,
inbound, toll-free, international, conference, service
(calls to 311/411/511/611/811/911) or unknown.
% curl -H "Accept: application/json;version=0" "https://api.ubity.com/cdr/2026/08/17?key=KKKK"
{
"api_key": "KKKK",
"cdrs": [
{
"id": "1755430000.1234",
"date": 1755430000000,
"from_number": "5145551212",
"from_ext": "",
"to_num": "5145550000",
"to_ext": "101",
"duration": 63,
"queue": "",
"conf_name": "",
"disposition": "ANSWERED",
"type": "inbound"
}
],
"code": 200,
"diagnostic": "Success",
"mode": "normal",
"stamp": "2026-08-18 10:00",
"url": "https://api.ubity.com/cdr/2026/08/17?key=KKKK",
"version": 0
}
Find the CDRs matching a recording
Given a call recording file name (as returned by the recordings endpoints), return the matching CDRs. The records have the same fields as above.
GET https://api.ubity.com/cdr_by_recording/<filename>
| Parameter | Description |
|---|---|
| key | Your Ubity API key |
% curl -H "Accept: application/json;version=0" "https://api.ubity.com/cdr_by_recording/1755430000.1234.mp3?key=KKKK"