Source note · The Webex Calling Detailed Call History API
The 2 Detailed Call History endpoints are indexed on different clocks: cdr_feed selects records by report time, which Cisco defines as the time the call finished, while cdr_stream selects them by the time the data was inserted into the Webex Calling cloud, which is why Cisco states that the stream automatically backfills late records into subsequent calls.
inferred · Checked 2026-09-15
It would be the earliest time at which the data was inserted into the Webex Calling cloud for the records you wish to collect.
- Vendor
- Cisco
- Product
- Webex Calling
- Subsystem
- Detailed Call History API
- Deployment
- not restricted
- Region
- not restricted
- Release range
- not restricted
- Status
- inferred
- Checked
- 2026-09-15
Sources
- Reports: Live Stream Detailed Call History — Get Live Stream Detailed Call History — Cisco Systems, Inc. (developer.webex.com) · tier 2 current vendor documentation · spec.parameters startTime description, against the cdr_feed startTime description on cisco-dev-cdr-feed-detailed-call-history
Cite this note
APA
WarmTransfer. (2026, September 15). The Webex Calling Detailed Call History API: source note wxcdrapi-feed-and-stream-index-different-times. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxcdrapi-feed-and-stream-index-different-times
BibTeX
@misc{warmtransfer-claim-wxcdrapi-feed-and-stream-index-different-times,
title = {The Webex Calling Detailed Call History API: source note wxcdrapi-feed-and-stream-index-different-times},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxcdrapi-feed-and-stream-index-different-times},
note = {Source note wxcdrapi-feed-and-stream-index-different-times, checked 2026-09-15}
}