Get CDR log

Reading Time: 3 minutes

Retrieve CDR log list, filtered according to given options.

Note: CDR data is generated immediately after a call ends, but a delay may occur between generating and registering the data, as it needs to be processed firstly (e.g. calculating costs).

Note: When using the resource, up to the first 10 items of the full list can be retrieved.

Tip: If you have not received a response, this may be due to a slowdown. We suggest querying the CDR data 5 minutes after sending the Webhook request. You can subsequently retry querying the CDR data every 5 minutes, up to a total of 20 times.

Method GET
Resource https://[customer][year]/[month]/[day]
Options projectid, start, num
Body N/A
Body Array of CDR objects, encoded in JSON.


Resource parameters

Name Type Mandatory Comment
customer string yes Your call centre’s unique identifier (subdomain).
year integer yes Year.
month integer yes Month within the requested year. Possible values:
– 01-12
day integer no Day within the requested month. Possible values:
– 01-31


Name Type Mandatory Comment
num integer no Specifies the maximum number of CDRs to be returned. Possible values:
– [0-9]+
projectid integer no Narrows down the scope of data to be searched in a given project.
start integer no Specifies the offset of the first CDR. Possible values:
– [0-9]+


Response object

Name Type Comment
rows array of object Array of CDR elements.
totalCount integer Number of CDRs for the given period.

CDR object

Name Type Comment
afterwork integer Duration/length of afterwork, in seconds.
beforequeuetime integer Time spent before the call is placed in a queue (e.g. time spent in IVR), in seconds.
billing_ts string Time the conversation begins, in YYYY-MM-DD hh-mm-ss format.
billingtime integer Length of complete call, in seconds (including ivr, queue and conversation time, but excluding ringtime).
destination string Called phone number.
dispositionid integer Unique disposition identifier in the database set for the call.
dispositionreach integer Disposition summary. Possible values:
– 1: not reached
– 2: reached
– 3: successful
dispositionstatus integer Disposition type. See: status key.
direction string Call direction:
– inbound
– outbound
holdtime integer Duration/length of hold, in seconds.
next_contact string The date and time when the system will try to call a specific phone number next.
numberid integer Unique record identifier in the database.
prework integer Duration/length of prework, in seconds.
projectid integer Unique project identifier in the database.
queuetime integer If the call is placed in a queue, then the time spent in the queue, in seconds.
ringtime integer Duration/length of ringing, in seconds.
source string Caller’s phone number.
start_ts string Time the call is initiated, in YYYY-MM-DD hh-mm-ss format.
talktime integer Time during the call in which talking takes place, in seconds.
userid integer Unique user identifier (-1 system, otherwise agent).
uuid string Unique call identifier.
queueid integer Queue’s indetifier.


List the first CDR in November, 2014.


Response body

    "response": {
        "rows": [
      "uuid": "d3c584b4-5f38-11e9-81be-eb8ee87cf8bf",
      "source": "3433335343",
      "shortid": "9S8G4J56",
      "destination": "3434334333",
      "userid": 0,
      "numberid": 0,
      "start_ts": "2019-04-15 06:42:08",
      "billing_ts": "2019-04-15 06:42:09",
      "ringtime": 0,
      "billingtime": 223,
      "talktime": 223,
      "queuetime": 0,
      "beforequeuetime": 0,
      "dispositionid": 0,
      "dispositionreach": 0,
      "dispositionstatus": 0,
      "projectid": 370,
      "holdtime": 0,
      "afterwork": 0,
      "prework": 0,
      "direction": "inbound",
      "sum_work": "00:03:43",
      "queueid": 0,
      "next_contact": "0000-00-00 00:00:00",
      "call_rate": "0.000000",
      "call_quantity": "3.716667",
      "currency": "huf",
      "dialermode": 1,
      "dc": 16,
      "disposition_comment": null,
      "pricetag": "hu-in-landline",
      "total_fee": "0.000000",
      "hangup_disposition": "operator",
      "vcc_score": null,
      "recordCustomFieldData": null,
      "statusArchived": "no",
      "lastArchivedTime": null,
      "trashUserId": null,
      "deletedUserId": null
        "totalCount": 1
    "errors": []

There are no comments yet.
Subscribe to our newsletter
or Contact us!
Please note that by subscribing to our newsletter, you agree to receive regular email messages from VCC Live® about service related news and updates. By subscribing to our newsletter, you also agree that VCC Live® will use your data in accordance with the applicable Privacy Policy until you unsubscribe from the newsletter.

Privacy Settings Center


Necessary cookies are essential in order to navigate around a website and use its basic features. You must accept these cookies as the website cannot function properly without them.



Marketing cookies are used to track visitors across websites and deliver advertisements that are more relevant and engaging to you.



Statistic cookies collect data to help us understand how visitors use our websites and are used to improve the user experience. These cookies don’t collect personal information and cannot identify visitors.



Other cookies are those cookies that do not fall into the categories above. These cookies are in the process of being classified.