Reports: Detailed Call History — Get Detailed Call History

Publisher

Cisco Systems, Inc. (developer.webex.com)

URL

https://developer.webex.com/calling/docs/api/v1/reports-detailed-call-history/get-detailed-call-history

Published

unknown

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

Cisco proprietary documentation, all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• A Webex developer API reference page carries no publication timestamp anywhere in its embedded page state: documentation.entry is null on such a page and the apiReference object that holds its content carries an API version number and no time field. field report in context
• Detailed Call History Answer reason displays Auto Answer when the Auto-Answer feature handled the call and N/A for a manually answered call, so the field distinguishes only 1 named answering mechanism from everything else. in context
• The Detailed Call History API returns 86 fields while the Control Hub Calling Detailed Call History Report publishes 87 columns, and the difference is 3 names: External customer ID and AI Agent ID appear only in the report, and Transfer type appears only in the API. in context
• Both Detailed Call History endpoints return 86 fields per record, and the 2 field sets are identical in membership and in order. in context
• Detailed Call History Call outcome reason documents 26 values under the 3 outcomes on the cdr_feed endpoint: 3 under Success, 15 under Refusal and 8 under Failure. in context
• Detailed Call History Call outcome carries 3 values, and Success is defined as a call routed and disconnected successfully including the Normal, UserBusy and NoAnswer scenarios, so a busy or unanswered call is recorded as a successful outcome; Failure means an internal or external error and Refusal means the call was rejected because of call block or timeout. in context
• The Detailed Call History Direction field is described as recording whether the call was inbound or outbound, and the 2 values it publishes are ORIGINATING and TERMINATING. field report in context
• The overview of the Webex Calling cdr_feed endpoint states that it can query any 12-hour period between 5 minutes ago and 30 days prior to the current UTC time, and gives a worked example in which a call ending at 9:46 AM becomes collectable at 9:51 AM and remains available until 9:46 AM 30 days later. disputed in context
• The startTime and endTime query parameters of the Webex Calling cdr_feed endpoint state that the specified time must be between 5 minutes ago and 48 hours ago, and that endTime should be later than startTime but no later than 48 hours. disputed in context
• The Detailed Call History API documentation directs a reader to the Control Hub report article for the fields it returns and their possible values, and that article does not publish 1 of the API's fields, Transfer type. inferred in context
• A Detailed Call History record carries 4 session UUIDs, Local SessionID, Remote SessionID, Final local SessionID and Final remote SessionID, described as usable for end-to-end tracking of a SIP session in compliance with RFC 7206 and draft-ietf-insipid-session-id-15; the Local value is generated by the originating user agent, the Remote value by the terminating user agent, and the 2 Final values are those values as they stood at the end of the call. in context
• Detailed Call History Interaction ID ties together multiple call patterns linked by a service interaction, and Cisco's worked example is a consult and transfer: when a user holds an active call, places another call from the same app or device and then transfers the original call, both calls share the same Interaction ID. in context
• Detailed Call History Local call ID is used with 2 other fields for 2 different purposes: with Remote call ID it identifies the remote record of the same call leg, and with Transfer related call ID it identifies the transferred leg. in context
• The locations query parameter on both Detailed Call History endpoints accepts up to 10 comma-separated location names as shown in Control Hub. in context
• The max parameter on both Detailed Call History endpoints ranges from 500 to 5000, values below 500 are automatically adjusted up to 500 and values above 5000 are automatically adjusted down to 5000, and the default is 5000. in context
• Detailed Call History Network call ID shows whether 2 records belong to the same call leg: 2 records belong to the same leg if and only if they carry the same Network call ID, and Report ID is described as a unique identifier for the individual record that can be used to deduplicate while processing. in context
• Detailed Call History pagination is carried in a Link response header whose next relation must be followed to obtain the next page, the absence of a next link means every record for the selected range has been collected, and the next link carries 2 parameters the caller's own request does not: startTimeForNextFetch and totalCount. in context
• Both Detailed Call History endpoints are rate limited to 1 initial request per minute per user token, with up to 10 additional pagination requests per minute per user token. in context
• Detailed Call History Redirect reason and Original reason publish the same 13 values, Redirect reason carrying the reason for the redirecting number and Original reason the reason for the original called number, and their value descriptions differ in 4 places, of which only 1 is substantive: Original reason adds Group night forwarding to the Unconditional value and Redirect reason does not. in context
• Detailed Call History Related call ID names a different call that this call created because of a service activation, and its value is the Local call ID of that related call. in context
• The Detailed Call History Related reason field documents 33 named values, and 2 of them are malformed as identifiers: CalllPark is spelled with 3 letter Ls, and Remote Office carries a space where every other value is a single unspaced token. field report in context
• Retrieving Detailed Call History requires both a token carrying the spark-admin:calling_cdr_read scope and an authenticating user whose administrator role has Webex Calling Detailed Call History API access enabled. in context
• 6 Detailed Call History field names are spelled differently by the API and by the Control Hub report while naming the same field: Client version against Client Version, Device MAC against Device Mac, Call transfer Time against Call transfer time, Final local SessionID against Final Local Session ID, Final remote SessionID against Final Remote Session ID, and PSTN Vendor Name against PSTN vendor name. field report in context
• The Detailed Call History Transfer type field is described as indicating the type of the transfer attempt, and both of its documented example values are AI Receptionist deflections: AI Receptionist Deflection By Intent for a call routed to a number mapped to an identified intent, and AI Receptionist Deflection By Default for a call routed to a preconfigured default number after a conversation outcome or a call failure. in context
• The Webex Calling Detailed Call History API publishes 2 endpoints on a host of its own, analytics-calling.webexapis.com: GET /v1/cdr_feed, which Cisco recommends for pulling records for a specific time period, and GET /v1/cdr_stream, which Cisco recommends as the primary API for continuously consuming records into custom reporting, analytics or an internal data store. in context
• 2 Detailed Call History Call outcome reason values name the local gateway: LocalGatewayLoop, a loop detected between the local gateway and Webex Calling, recorded as a Refusal, and MaxConcurrentTerminatingAlertingRequestsExceeded, the number of simultaneous unanswered calls to a local gateway for the same calling and called number exceeding the limit, recorded as a Failure. in context
• A Detailed Call History request routed to a region that does not host the organisation's data returns HTTP 451, and Cisco states that the response body then carries endpoint information indicating where the organisation's data can be retrieved; 4 regional hostnames are published, for United States and Canada, Europe, India and Australia. in context
• None of the 86 fields the Webex Calling Detailed Call History API returns is a media quality metric: no field name and no field description in the endpoint's schema mentions jitter, packet loss, latency, round trip time, mean opinion score or media quality. in context

Cite this source record

APA

WarmTransfer. (2026, September 16). Reports: Detailed Call History — Get Detailed Call History. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-dev-cdr-feed-detailed-call-history

BibTeX

@misc{warmtransfer-cisco-dev-cdr-feed-detailed-call-history,
  title  = {Reports: Detailed Call History — Get Detailed Call History},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-dev-cdr-feed-detailed-call-history},
  note   = {Cisco Systems, Inc. (developer.webex.com), accessed 2026-09-16}
}