We recommend using the CDR stream endpoint as the primary API for customers who need to continuously consume CDRs for custom reporting, analytics applications, or integration into internal data stores.

The CDR Stream endpoint will allow customers to call the API as soon as the call ends, typically 1 minute before the current time. It automatically backfills any late records as soon as they are processed in the Webex Calling cloud. These records are then delivered in subsequent API calls, ensuring reliable CDR delivery.

To retrieve Detailed Call History information, you must use a token with the spark-admin:calling_cdr_read scope. The authenticating user must have the administrator role "Webex Calling Detailed Call History API access" enabled.

Detailed Call History information is available 1 minute after the call ends and the data reaches Webex Calling cloud. Records may be retrieved for up to 12 hours from the time they are stored. For example: if a call's data reaches the Webex Calling cloud at 9:46 AM, the record becomes available from 9:47 AM and remains retrievable until 9:46 PM the same day. Additionally, only 2 hours’ worth of records can be retrieved per request (i.e., 2 hours between the selected start and end times in a single API call).

This API is rate-limited to 1 initial request per minute per user token, with up to 10 additional pagination requests per minute per user token.

Details on the returned fields and their possible values are available at https://help.webex.com/en-us/article/nmug598/Reports-for-Your-Cloud-Collaboration-Portfolio. Select the Report templates tab, then under Webex Calling reports, see Calling Detailed Call History Report.

By default, requests to analytics-calling.webexapis.com are routed to the closest region's servers. If those servers host the organization’s data, the data is returned. Otherwise, an HTTP 451 error code is returned. In such cases, the response body contains endpoint information indicating where the organization’s data can be retrieved.