DocumentationBlogSupport
Log inSign up
Log inSign up
BlogSupport
Build
Getting StartedPlatform Introduction
Embedded Apps
What's NewOverviewDeveloper GuideSidebar API Quick StartSubmission Checklist for Embedded Apps
Design Guidelines
MessagingMeetingsDevicesSidebarSidebar on Mobile
API Reference
BotsButtons and CardsIntegrationsBYODSService AppsService App GuestsService Apps G2GGuest IssuerWidgetsWebex ConnectLogin with WebexInstant ConnectInstant Connect Meeting LinksDeveloper SandboxBeta ProgramSubmit Your AppSupport PolicyFAQs
APIs
API Behavior ChangesPartners API GuideXML API DeprecationAccess the APIREST API BasicsCompliance
Webex APIs
Reference
Data Sources
Admin
OverviewAdmin APIsHybrid ServicesAuthentication
Guides
Hybrid ServicesWebhooksReal-time File DLP BasicsProvisioning APIsBackground ImagesAudit Events Error Reference
Reference
Admin Audit EventsAuthorizationsEventsGroupsHistorical AnalyticsHybrid ClustersHybrid ConnectorsLicensesMeeting QualitiesOrganization ContactsOrganizationsPartner ManagementPartner Reports/TemplatesPartner TagsPeopleRecording ReportRecordingsReport TemplatesReportsResource Group MembershipsResource GroupsRolesSecurity Audit EventsSession TypesSettingsSpace ClassificationsTracking CodesWorkspace LocationsWorkspace Metrics
Webex Calling Beta
Overview
Guides
Integrations and AuthorizationMetadata and Samples
Webex Calling
OverviewSDKs and ToolsWhat's New
Guides
Integrations and AuthorizationProvisioning APIsMetadata and SamplesBackground Images
Reference
Call ControlsCall RoutingCall Settings For MeCalling Service SettingsClient Call SettingsConference ControlsConverged RecordingsDECT Devices SettingsDevice Call SettingsDevicesEmergency Services SettingsFeatures: Announcement PlaylistFeatures: Announcement RepositoryFeatures: Auto AttendantFeatures: Call ParkFeatures: Call PickupFeatures: Call QueueFeatures: Call RecordingFeatures: Customer Experience EssentialsFeatures: Hunt GroupFeatures: Operating ModesFeatures: Paging GroupFeatures: Single Number ReachLocation Call SettingsLocation Call Settings: Call HandlingLocation Call Settings: SchedulesLocation Call Settings: VoicemailLocationsNumbersPSTNPartner Reports/TemplatesPeopleRecording ReportReportsReports: Detailed Call History
GETGet Detailed Call History
Send Activation EmailUser Call SettingsVirtual Line Call SettingsWorkspace Call SettingsWorkspaces
Webex for Broadworks
Overview
Guides
Integrations and AuthorizationDeveloper's Guide
Reference
BroadWorks Billing ReportsBroadWorks EnterprisesBroadWorks SubscribersBroadWorks Workspaces
Webex for Wholesale
Overview
Guides
Developer's Guide
Reference
Wholesale Billing ReportsWholesale Provisioning
Webex for UCM
Guides
Integrations and Authorization
Reference
UCM Profile
Contact Center
Overview
Reference
Data Sources
Customer Journey Data
Overview
Guides
Getting StartedFAQ
Devices
Overview
Guides
Devices
Reference
Device Call SettingsDevice ConfigurationsDevicesWorkspace LocationsWorkspace MetricsWorkspace PersonalizationWorkspacesxAPI
Directory Services
Reference
Domain ManagementIdentity Organization
Meetings
Overview
Guides
Integrations and AuthorizationWebhooksWebinar GuideMeeting Resource Guide
Reference
Meeting ChatsMeeting Closed CaptionsMeeting InviteesMeeting MessagesMeeting ParticipantsMeeting PollsMeeting PreferencesMeeting Q and AMeeting QualitiesMeeting TranscriptsMeetingsMeetings Summary ReportPeopleRecording ReportRecordingsSession TypesTracking CodesVideo MeshWebhooks
Messaging
Overview
Guides
BotsIntegrations and AuthorizationWebhooksButtons and Cards
Reference
Attachment ActionsEventsMembershipsMessagesPeopleRoom TabsRoomsTeam MembershipsTeamsWebhooks
SCIM 2
Overview
Reference
SCIM 2 BulkSCIM 2 GroupsSCIM 2 Users
Workspace Integrations
OverviewTechnical DetailsControl Hub Features
Webex Status API
Full API Reference
Admin Audit EventsAttachment ActionsAuthorizationsBroadWorks Billing ReportsBroadWorks EnterprisesBroadWorks SubscribersBroadWorks WorkspacesCall ControlsCall RoutingCall Settings For MeCalling Service SettingsClient Call SettingsConference ControlsConverged RecordingsDECT Devices SettingsData SourcesDevice Call SettingsDevice ConfigurationsDevicesDomain ManagementEmergency Services SettingsEventsFeatures: Announcement PlaylistFeatures: Announcement RepositoryFeatures: Auto AttendantFeatures: Call ParkFeatures: Call PickupFeatures: Call QueueFeatures: Call RecordingFeatures: Customer Experience EssentialsFeatures: Hunt GroupFeatures: Operating ModesFeatures: Paging GroupFeatures: Single Number ReachGroupsGuests ManagementHistorical AnalyticsHybrid ClustersHybrid ConnectorsIdentity OrganizationIssuesLicensesLocation Call SettingsLocation Call Settings: Call HandlingLocation Call Settings: SchedulesLocation Call Settings: VoicemailLocationsMeeting ChatsMeeting Closed CaptionsMeeting InviteesMeeting MessagesMeeting ParticipantsMeeting PollsMeeting PreferencesMeeting Q and AMeeting QualitiesMeeting TranscriptsMeetingsMeetings Summary ReportMembershipsMessagesNumbersOrganization ContactsOrganizationsPSTNPartner ManagementPartner Reports/TemplatesPartner TagsPeopleRecording ReportRecordingsReport TemplatesReportsReports: Detailed Call History
GETGet Detailed Call History
Resource Group MembershipsResource GroupsRolesRoom TabsRoomsSCIM 2 BulkSCIM 2 GroupsSCIM 2 UsersSecurity Audit EventsSend Activation EmailSession TypesSettingsSiteSpace ClassificationsTeam MembershipsTeamsTracking CodesUCM ProfileUser Call SettingsVideo MeshVirtual Line Call SettingsWebhooksWholesale Billing ReportsWholesale ProvisioningWorkspace Call SettingsWorkspace LocationsWorkspace MetricsWorkspace PersonalizationWorkspacesxAPI
API Changelog
SDKs
Space Meetings Migration
Calling
Introduction
Platform
Web
IntroductionQuickstart
Basics
AuthorizationCore ConceptsCalls
Advanced Features
Call SettingsContactsSupplementary ServicesVoicemailBackground Noise Reduction
Kitchen Sink
Meetings
Introduction
Platform
Web
IntroductionQuickstart
Basics
AuthorizationJoin a MeetingMigration To Improved MeetingsPasswords & CaptchasUnified Space Meetings
Advanced Features
Advanced ControlsDialing In and OutStreams & EffectsVideo Resolution
Multistream
Multistream Comprehensive GuideMultistream Quickstart
Migrating SDK V2 to V3
iOSAndroidBrowserNode.jsClick to Call
Developer CommunityCertifications

Get Detailed Call History

Provides Webex Calling Detailed Call History data for your organization.

Results can be filtered with the startTime, endTime and locations request parameters. The startTime and endTime parameters specify the start and end of the time period for the Detailed Call History reports you wish to collect. The API will return all reports that were created between startTime and endTime.



Response entries may be added as more information is made available for the reports. Values in response items may be extended as more capabilities are added to Webex Calling.

GET/v1/cdr_feed
Query Parameters
startTime
stringrequired

Time of the first report you wish to collect. (Report time is the time the call finished). Note: The specified time must be between 5 minutes ago and 48 hours ago, and be formatted as YYYY-MM-DDTHH:MM:SS.mmmZ.

endTime
stringrequired

Time of the last report you wish to collect. (Report time is the time the call finished). Note: The specified time should be later than startTime but no later than 48 hours, and be formatted as YYYY-MM-DDTHH:MM:SS.mmmZ.

locations
string

Name of the location (as shown in Control Hub). Up to 10 comma-separated locations can be provided. Allows you to query reports by location.

max
number

Limit the maximum number of reports per page of the response. The range is 1 to 500. When the API has more reports to return than the max value, the API response will be paginated. Follow the next link contained in the “Link” header within a response to request the next page of results. If there is no next link, all reports for the selected time range have been collected. API requests for the next pages can be requested immediately and do not count towards API rate limiting.

Default: 500
Response Properties
items
array[CDR]
Answer indicator
string

Whether the call leg was answered after a redirection. Possible values:

  • Yes

  • No

  • Yes-PostRedirection

Answer time
string

The time the call was answered. Time is in UTC.

Answered
string

Whether the call leg was answered. For example, in a hunt group case, some legs will be unanswered, and one will be answered.

Authorization code
string

The authorization code admin created for a location or site for users to use. Collected by the Account/Authorization Codes or Enhanced Outgoing Calling Plan services.

Call ID
string

SIP Call ID used to identify the call. You can share the Call ID with Cisco TAC to help them pinpoint a call if necessary.

Caller ID number
string

Displays the calling party’s presentation number based on the caller ID setting from Control Hub. Can be a line/extension, location number, or a custom organization option.

  • The Caller ID number is not restricted to E.164 format and can vary based on system configuration.

  • For redirected calls, represents only the redirecting party's caller ID number.

Call outcome
string

Identifies whether the call was set up or disconnected normally. Possible values:

  • Success: Call is routed and disconnected successfully. Includes Normal, UserBusy, and NoAnswer scenarios.

  • Failure: Call failed with an internal or external error.

  • Refusal: Call is rejected because of call block or timeout. You can find more information in the Call outcome reason field.

Call outcome reason
string

Additional information about the Call outcome returned. Possible reasons are:

  • Success

    • Normal: Call is completed successfully.
    • UserBusy: Call is a success, but the user is busy.
    • NoAnswer: Call is a success, but the user didn't answer.
  • Refusal

    • CallRejected: The call recipient didn’t want to receive the call and rejected the call.
    • UnassignedNumber: The dialed number isn't assigned to any user or service.
    • SIP408: Request timed out because couldn’t find the user in time.
    • InternalRequestTimeout: Request timed out as the service couldn’t fulfill the request due to an unexpected condition.
    • Q850102ServerTimeout: Recovery on timer expiry/server timed out
    • NoUserResponse: No response from any end-user device/client
    • NoAnswerFromUser: No answer from the user.
    • SIP480: Callee or called party is currently unavailable.
    • SIP487: Request is terminated by bye or cancel.
    • TemporarilyUnavailable: User is temporarily unavailable.
    • AdminCallBlock: Call attempt is rejected by an upstream intermediary machine, process or human.
    • UserCallBlock: Call attempt from a client is rejected or blocked by the user.
    • Unreachable: Unable to route the call to the desired destination.
  • Failure

    • DestinationOutOfOrder: Service request failed as the destination can’t be reached or the interface to the destination isn’t functioning correctly.
    • SIP501: Invalid method and can’t identify the request method.
    • SIP503: Service is temporarily unavailable so can’t process the request.
    • ProtocolError: Unknown or unimplemented release code.
    • SIP606: Some aspect of the session description wasn't acceptable.
    • NoRouteToDestination: No route available to the destination
    • Internal: Failed because of internal Webex Calling reasons.
Call Recording Platform Name
string

Call recording Platform Name and the recording platform can be "DubberRecorder", "Webex" or "Unknown" if the Call Recording Platform Name could not be fetched. Other supported vendors include "Eleveo", "ASCTech", "MiaRec", and "Imagicle".

Call Recording Result
string

Status of the recorded media: "successful", "failed", or "successful but not kept."

Call Recording Trigger
string

User's recording mode for the call. The values for this field are "always", always-pause-resume", "on-demand", or "on-demand-user-start."

Call transfer Time
string

Indicates the time at which the call transfer service was invoked during the call. The invocation time is shown using the UTC/GMT time zone format.

Call type
string

Type of call. For example:

  • SIP_MEETING

  • SIP_INTERNATIONAL

  • SIP_SHORTCODE

  • SIP_INBOUND

  • UNKNOWN

  • SIP_EMERGENCY

  • SIP_PREMIUM

  • SIP_ENTERPRISE

  • SIP_TOLLFREE

  • SIP_NATIONAL

  • SIP_MOBILE

Called line ID
string

For incoming calls, the calling line ID of the user. For outgoing calls, it's the calling line ID of the called party.

Called number
string

For incoming calls, the telephone number of the user. For outgoing calls, it's the telephone number of the called party.

Calling line ID
string

For incoming calls, the calling line ID of the calling party. For outgoing calls, it's the calling line ID of the user.

Calling number
string

For incoming calls, the telephone number of the calling party. For outgoing calls, it's the telephone number of the user.

Client type
string

The type of client that the user (creating this record) is using to make or receive the call. For example:

  • SIP

  • WXC_CLIENT

  • WXC_THIRD_PARTY

  • TEAMS_WXC_CLIENT

  • WXC_DEVICE

  • WXC_SIP_GW

Client version
string

The version of the client that the user (creating this record) is using to make or receive the call.

Correlation ID
string

Correlation ID to tie together multiple call legs of the same call session.

Department ID
string

A unique identifier for the user's department name.

Device MAC
string

The MAC address of the device, if known.

Device owner UUID
string

When calls are made using multi-line or shared line options, this field represents the unique identifier of the device owner. It holds the UUID from the Cisco Common Identity associated with the user. For example, if Alice has a device assigned and makes or receives a call from Bob's line, the CDR will show Alice's UUID as the device owner.

  • Only set when the device owner is different than the owner of the device who made/received the call.
Dialed digits
string

The keypad digits as dialed by the user, before pre-translations. This field reports multiple call dial possibilities:

  • Feature access codes (FAC) used for invoking features such as Last Number Redial or a Call Return.

  • An extension that got dialed and a mis-dialed keypad digit from a device/app.

  • When a user must dial an outside access code (for example, 9+) before dialing a number, this access code is also reported, as well as the digits dialed thereafter. Note that when pre-translations have no effect, the dialed digits field contains the same data as the called number field. This field is only used for originating (outgoing) Calls and is not available for terminating (incoming) Calls.

Direction
string

Whether the call was inbound or outbound. The possible values are:

  • ORIGINATING

  • TERMINATING

Duration
number

The length of the call in seconds.

External caller ID number
string

Set only when the control hub External Caller ID phone number is a location number or another number from the organization. Not set when "Direct line/Ext" options are selected.

  • Only included in originating CDRs (not present in terminating CDRs).

  • Not set for calls that are redirected

Final local SessionID
string

Each call consists of four UUIDs known as Local Session ID, Final Local Session ID, Remote Session ID and Final Remote Session ID.

  • The Session ID comprises a Universally Unique Identifier (UUID) for each user-agent participating in a call.

  • It can be used for end-to-end tracking of a SIP session in IP-based multimedia communication systems in compliance with RFC 7206 and draft-ietf-insipid-session-id-15.

  • The Local SessionID is generated from the Originating user agent.

  • The Remote SessionID is generated from the Terminating user agent.

  • The Final Local Session ID has the value of the Local Session ID at the end of the call.

  • The Final Remote Session ID has the value of the Remote Session ID at the end of the call.

Final remote SessionID
string

Each call consists of four UUIDs known as Local Session ID, Final Local Session ID, Remote Session ID and Final Remote Session ID.

  • The Session ID comprises a Universally Unique Identifier (UUID) for each user-agent participating in a call.

  • It can be used for end-to-end tracking of a SIP session in IP-based multimedia communication systems in compliance with RFC 7206 and draft-ietf-insipid-session-id-15.

  • The Local SessionID is generated from the Originating user agent.

  • The Remote SessionID is generated from the Terminating user agent.

  • The Final Local Session ID has the value of the Local Session ID at the end of the call.

  • The Final Remote Session ID has the value of the Remote Session ID at the end of the call.

Inbound trunk
string

Inbound trunk may be presented in Originating and Terminating records.

International country
string

The country code of the dialed number. This is only populated for international calls.

Local call ID
string

A unique identifier that is used to correlate CDRs and call legs with each other. This ID is used in conjunction with:

  • Remote call ID: To identify the remote CDR of a call leg.

  • Transfer related call ID: To identify the call transferred leg.

Local SessionID
string

Each call consists of four UUIDs known as Local Session ID, Final Local Session ID, Remote Session ID and Final Remote Session ID.

  • The Session ID comprises a Universally Unique Identifier (UUID) for each user-agent participating in a call.

  • It can be used for end-to-end tracking of a SIP session in IP-based multimedia communication systems in compliance with RFC 7206 and draft-ietf-insipid-session-id-15.

  • The Local SessionID is generated from the Originating user agent.

  • The Remote SessionID is generated from the Terminating user agent.

  • The Final Local Session ID has the value of the Local Session ID at the end of the call.

  • The Final Remote Session ID has the value of the Remote Session ID at the end of the call.

Location
string

Location of the report.

Model
string

The device model type the user is using to make or receive the call.

Network call ID
string

A unique identifier that shows if other CDRs are in the same call leg. Two CDRs belong in the same call leg if they have the same Network call ID.

Org UUID
string

A unique identifier for the organization that made the call. This is a unique identifier across Cisco.

Original reason
string

Call redirection reason for the original called number. For example:

  • Unconditional: Call Forward Always (CFA) service, Group night forwarding.

  • NoAnswer: The party was not available to take the call. CF/busy or Voicemail/busy.

  • Deflection: Indication that a call was redirected. Possible causes could be Blind transfer, Auto attendant transfer, Transfer out of a Call center etc.

  • TimeOfDay: Automated redirection based on the time of the call. Call Forwarding Selective, Call Forwarding mode-based, or Group Night.

  • UserBusy: DND enabled or the user willingly declined the call. CF/busy or voicemail/busy.

  • FollowMe: Automated redirection to a personal redirecting service which could be Simultaneous Ringing, Sequential Ringing, Office Anywhere, or Remote Office.

  • CallQueue: A call center call to an agent or a user (a member of the call queue).

  • HuntGroup: A hunt-group-based call to an agent or a user (denotes a member of the hunt group).

  • Unavailable: To voicemail, when the user has no app or device.

  • Unrecognized: Unable to determine the reason.

  • Unknown: Call forward by phone with no reason.

  • ExplicitIdxxx: Enterprise voice portal redirection to the user’s home voice portal. The “xxx” portion is the digits collected from the caller, identifying the target mailbox (Extension or DN).

  • ImplicitId: Indicates an enterprise voice portal redirection to the user’s home voice portal.

OS type
string

The operating system that the app was running on, if available.

Outbound trunk
string

Outbound trunk may be presented in Originating and Terminating records.

Public Called IP Address
string

Public IP address of the terminating device or application that is assigned with an Internet Telephony Number.

Public Calling IP Address
string

Public IP address of the device or application making a call that is assigned with an Internet Telephony Number.

Release time
string

The time the call was finished, in UTC.

Ring duration
number

The length of ringing before the call was answered or timed out, in seconds.

Redirecting party UUID
string

When a call is redirected one or more times, indicates the unique identifier of the last redirecting party user or service accountable for the CDR. Holds the value of the UUID contained in the Cisco Common Identity associated with a user or service.

Redirect reason
string

Call Redirection Reason for the redirecting number. For example:

  • Unconditional: Call Forward Always (CFA) service.

  • NoAnswer: The party was not available to take the call. CF/busy or Voicemail/busy.

  • Deflection: Indication that a call was redirected. Possible causes could be Blind transfer, Auto attendant transfer, Transfer out of a Call center etc.

  • TimeOfDay: Automated redirection based on the time of the call. Call Forwarding Selective, Call Forwarding Mode-Based, or Group Night

  • UserBusy: DND enabled or user willingly declined the call. CF/busy or Voicemail/busy.

  • FollowMe: Automated redirection to a personal redirecting service which could be Simultaneous Ringing, Sequential Ringing, Office Anywhere, or Remote Office.

  • CallQueue: A call center call to an agent or a user (denotes a member of the call queue).

  • HuntGroup: A hunt-group-based call to an agent or a user (denotes a member of the hunt group).

  • Unavailable: To voicemail, when the user has no app or device.

  • Unrecognized: Unable to determine the reason.

  • Unknown: Call forward by phone with no reason.

  • ExplicitIdxxx: Enterprise voice portal redirection to the user’s home voice portal. The “xxx” portion is the digits collected from the caller, identifying the target mailbox (Extension or DN).

  • ImplicitId: Indicates an enterprise voice portal redirection to the user’s home voice portal.

Redirecting number
string

When the call has been redirected one or more times, this field reports the last redirecting number. Identifies who last redirected the call. Only applies to call scenarios such as transfer, call forwarded calls, simultaneous rings, etc.

Related call ID
string

Call identifier of a different call that was created by this call because of a service activation. The value is the same as the Local call ID field of the related call. You can use this field to correlate multiple call legs connected through other services.

Related reason
string

Indicates a trigger that led to a change in the call presence. The trigger could be for this particular call or redirected via a different call. For example:

  • ConsultativeTransfer: While on a call, the call was transferred to another user by announcing it first. meaning the person was given a heads up or asked if they're interested in taking the call and then transferred.

  • CallForwardModeBased: Calls are forwarded using the mode-based management feature option.

  • CallForwardSelective: Call Forward as per the defined schedule. Might be based on factors like a specific time, specific callers or to a VM. It always takes precedence over Call Forwarding.

  • CallForwardAlways: Calls are unconditionally forwarded to a defined phone number or to VM.

  • CallForwardNoAnswer: The party was not available to take the call.

  • CallQueue: A call center call to an agent or a user (denotes a member of the call queue).

  • HuntGroup: A hunt group based call to an agent or a user (denotes a member of the hunt group).

  • CallPickup: The user part of a pickup group or pickup attempted by this user against a ringing call for a different user or extension.

  • CalllPark: An ongoing call was parked, assigned with a parked number (not the user’s phone number).

  • CallParkRetrieve: Call park retrieval attempt by the user, either for a different extension or against the user’s own extension.

  • Deflection: Indication that a call was redirected. Possible causes could be Blind transfer, Auto-attendant transfer, Transfer out of a Call center, etc.

  • FaxDeposit: Indicates a FAX was transmitted to the FAX service.

  • PushNotificationRetrieval: Push notification feature usage indication. Means that a push notification was sent to wake up the client and get ready to receive a call.

  • BargeIn: Indicates the user barged-in to someone else’s call.

  • VoiceXMLScriptTermination: Route Point feature usage indication.

  • AnywhereLocation: Indicates call origination towards the single number reach location.

  • AnywherePortal: Indicates call origination towards the “user” identified by the single number reach portal.

  • Unrecognized: Unable to determine the reason.

  • CallForwardBusy: The user willingly declined the call, or DND was enabled that then redirected the call to a defined phone number or voice mail.

  • CallForwardNotReachable: Hunt group redirection for an agent who is not reachable.

  • CallRetrieve: The user triggered the call retrieve option to pick up a call that was parked.

  • CallRecording: The user initiated the call recording service that triggered Start/Pause/Resume/Stop recording options.

  • DirectedCallPickup: Indicates this user belonged to a call pickup group who answered the call or answered when another member of the call pickup group in a location was busy.

  • Executive: The user has been configured using the Executive/Executive assistant service who is allowed to handle calls on someone else's behalf. Also known as Boss-admin.

  • ExecutiveAssistantInitiateCall: The user has been configured as an Executive assistant who placed or initiated the call on someone else’s (Boss admin's) behalf.

  • ExecutiveAssistantDivert: The user has been configured as an Executive assistant who had call forwarding enabled to a defined phone number.

  • ExecutiveForward: The Executive (Boss-admin) had a call forward setting enabled to a defined number. Generally triggered when an ExecutiveAssistant did not pick a call.

  • ExecutiveAssistantCallPush: The user has been configured as an Executive assistant who received a call and pushed that call out (using #63) to the Executive’s (Boss-admin's) number.

  • Remote Office: Indicates the call was made to reach the remote location of the user.

  • RoutePoint: Indicates an incoming and queued call to an agent (for incoming calls to the route point).

  • SequentialRing: Indicates this user is in the list of phone numbers, which are alerted sequentially upon receiving an incoming call that matches a set of criteria.

  • SimultaneousRingPersonal: Indicates this user was in the list of multiple destinations that are to ring simultaneously when any calls are received on their phone number (the first destination answered is connected).

  • CCMonitoringBI: The indication that a Call Queue supervisor invoked silent monitoring.

Releasing party
string

Indicates which party released the call first. The possible values are:

  • Local: Used when the local user has released the call first.

  • Remote: Used when the far-end party releases the call first.

  • Unknown: Used when the call has partial information or is unable to gather enough information about the party who released the call. It could be because of situations like force lock or because of a session audit failure.

Remote call ID
string

A unique identifier that is used to correlate CDRs and call legs with each other. This ID is used in conjunction with Local call ID to identity the local CDR of a call leg.

Remote SessionID
string

Each call consists of four UUIDs known as Local Session ID, Final Local Session ID, Remote Session ID and Final Remote Session ID.

  • The Session ID comprises a Universally Unique Identifier (UUID) for each user-agent participating in a call.

  • It can be used for end-to-end tracking of a SIP session in IP-based multimedia communication systems in compliance with RFC 7206 and draft-ietf-insipid-session-id-15.

  • The Local SessionID is generated from the Originating user agent.

  • The Remote SessionID is generated from the Terminating user agent.

  • The Final Local Session ID has the value of the Local Session ID at the end of the call.

  • The Final Remote Session ID has the value of the Remote Session ID at the end of the call.

Report ID
string

A unique ID for this particular record. This can be used when processing records to aid in deduplication.

Report time
string

The time this report was created. Time is in UTC.

Route group
string

If present, this field's only reported in Originating records. Route group identifies the route group used for outbound calls routed via a route group to Premises-based PSTN or an on-prem deployment integrated with Webex Calling (dial plan or unknown extension).

Site main number
string

The main number for the user's site where the call was made or received.

Site timezone
string

Site timezone is the offset in minutes from UTC time of the user's timezone.

Site UUID
string

A unique identifier for the site associated with the call. Unique across Cisco products.

Start time
string

This is the start time of the call, the answer time may be slightly after this. Time is in UTC.

Sub client type
string

If the call is TO or FROM a mobile phone using Webex Go, the Client type will show SIP, and Sub client type will show MOBILE_NETWORK.

Transfer related call ID
string

Call identifier of a different call that was involved in the transfer. You can share this ID with Cisco TAC to help them pinpoint parties who were involved in the call transfer.

User
string

Represents the display name for the user type involved in the call, such as User, Workspace, Virtual Line, Auto Attendant, or Call Queue.

User number
string

Represents the E.164 number of the user generating a CDR. If the user has no number assigned to them, then their extension will be displayed instead.

User type
string

The type of user (user or workspace) that made or received the call. For example:

  • AutomatedAttendantVideo: Automated Attendant Video IVR group service.

  • Anchor: A Webex Calling user number made or received that is integrated with Webex Contact Center. An "anchor" is created to facilitate the call routing flow between WxC and WxCC.

  • BroadworksAnywhere: Single number reach (Office anywhere) service.

  • VoiceMailRetrieval: Voice Mail group service.

  • LocalGateway: A local gateway-based user who made or received the call.

  • HuntGroup: A hunt group based service.

  • GroupPaging: One way call or group page made for target users.

  • User: The direct user who made or received the call.

  • VoiceMailGroup: Shared voicemail or inbound FAX destination for users.

  • CallCenterStandard: A call queue-based service.

  • VoiceXML: Call added back to the Route Point queue after script termination.

  • RoutePoint: Route Point call to an agent (for an incoming call to the routing point).

  • Place: A workspace-based user who made or received the call.

  • VirtuaLline: Call made or received by a virtual line user using the Multi-line option in Webex Calling.

User UUID
string

A unique identifier for the user associated with the call. This is a unique identifier across Cisco products.

PSTN Vendor Name
string

Displays the name of the vendor from which one has purchased PSTN service for a specific country. For example:

  • If purchased from Cisco PSTN, the field would display "Cisco Calling Plans"

  • If purchased from Cisco Cloud Connected PSTN Partners, the field would list names such as "Tata", "IntelePeer", "KDDI", etc.

PSTN Legal Entity
string

This field shows the regulated business entity registered to provide PSTN service in a particular country. It is exclusively used for Cisco Calling Plans.

  • Note: The name of the regulated entity may vary within a region and across different regions.
PSTN Vendor Org ID
string

This field displays the organization's Universal Unique Identifier (UUID) for Cisco Calling Plans, which is unique across various regions.

PSTN Provider ID
string

This field represents an immutable UUID, as defined by Cisco, for a PSTN provider partner. It uniquely identifies the entity that has provided PSTN service in that country.

Response Codes

The list below describes the common success and error responses you should expect from the API:

CodeStatusDescription
200OKSuccessful request with body content.
201CreatedThe request has succeeded and has led to the creation of a resource.
202AcceptedThe request has been accepted for processing.
204No ContentSuccessful request without body content.
400Bad RequestThe request was invalid or cannot be otherwise served. An accompanying error message will explain further.
401UnauthorizedAuthentication credentials were missing or incorrect.
403ForbiddenThe request is understood, but it has been refused or access is not allowed.
404Not FoundThe URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.
405Method Not AllowedThe request was made to a resource using an HTTP request method that is not supported.
409ConflictThe request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.
410GoneThe requested resource is no longer available.
415Unsupported Media TypeThe request was made to a resource without specifying a media type or used a media type that is not supported.
423LockedThe requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again.
428Precondition RequiredFile(s) cannot be scanned for malware and need to be force downloaded.
429Too Many RequestsToo many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made.
500Internal Server ErrorSomething went wrong on the server. If the issue persists, feel free to contact the Webex Developer Support team.
502Bad GatewayThe server received an invalid response from an upstream server while processing the request. Try again later.
503Service UnavailableServer is overloaded with requests. Try again later.
504Gateway TimeoutAn upstream server failed to respond on time. If your query uses max parameter, please try to reduce it.
  • Try it
  • Example
GET
/v1/cdr_feed{?startTime,endTime,locations,max}
Log in to try the API.
Header
Query Parameters
  • Time of the first report you wish to collect. (Report time is the time the call finished). **Note:** The specified time must be between 5 minutes ago and 48 hours ago, and be formatted as `YYYY-MM-DDTHH:MM:SS.mmmZ`.
  • Time of the last report you wish to collect. (Report time is the time the call finished). **Note:** The specified time should be later than `startTime` but no later than 48 hours, and be formatted as `YYYY-MM-DDTHH:MM:SS.mmmZ`.
  • Name of the location (as shown in Control Hub). Up to 10 comma-separated locations can be provided. Allows you to query reports by location.
  • Limit the maximum number of reports per page of the response. The range is 1 to 500. When the API has more reports to return than the max value, the API response will be paginated. Follow the next link contained in the “Link” header within a response to request the next page of results. If there is no next link, all reports for the selected time range have been collected. API requests for the next pages can be requested immediately and do not count towards API rate limiting.
  • Request
  • Response
https://analytics.webexapis.com/v1/cdr_feed?startTime=2022-06-08T21:27:00.604Z&endTime=2022-06-09T23:27:18.604Z&locations=Erlanger%20Urgent%20/%20Primary%20Care%20Main&max=100
200 / OK
{
  "items": [
    {
      "Answer indicator": "Yes",
      "Answer time": "2020-05-14T11:01:17.551Z",
      "Answered": "true",
      "Authorization code": "107",
      "Call ID": "SSE1101163211405201218829100@10.177.4.29",
      "Caller ID number": "2003",
      "Call outcome": "Success",
      "Call outcome reason": "Normal",
      "Call Recording Platform Name": "Webex",
      "Call Recording Result": "successful",
      "Call Recording Trigger": "always",
      "Call transfer Time": "2023-06-05T18:21:29.707Z",
      "Call type": "SIP_ENTERPRISE",
      "Called line ID": "CALLEDCLIDGOESHERE",
      "Called number": "2002",
      "Calling line ID": "YOURCLIDGOESHERE",
      "Calling number": "2001",
      "Client type": "SIP_TOLLFREE",
      "Client version": "1.0.2.3",
      "Correlation ID": "8e8e1dc7-4f25-4595-b9c7-26237f824535",
      "Department ID": "4370c763-81ec-403b-aba3-626a7b1cf264",
      "Device MAC": "6C710D8ABC10",
      "Device owner UUID": "1e9e14c7-4f25-4595-b9c7-26237f824536",
      "Dialed digits": "1246",
      "Direction": "ORIGINATING",
      "Duration": 36,
      "External caller ID number": "2004",
      "Final local SessionID": "82bb753300105000a0000242be131609",
      "Final remote SessionID": "cfe67b8a00105000a0000242be131609",
      "Inbound trunk": "InTrunk",
      "International country": "US",
      "Local call ID": "113104021:0",
      "Local SessionID": "82bb753300105000a0000242be131609",
      "Location": "Richardson",
      "Model": "8851-3PCC",
      "Network call ID": "BW2356451711108231501755806@10.21.0.192",
      "Org UUID": "408806bc-a013-4a4b-9a24-85e374912102",
      "Original reason": "UserBusy",
      "OS type": "na",
      "Outbound trunk": "OutTrunk",
      "Public Called IP Address": "0.0.0.0",
      "Public Calling IP Address": "0.0.0.0",
      "Release time": "2023-10-12 21:22:32.621",
      "Ring duration": 23,
      "Redirecting party UUID": "afgh",
      "Redirect reason": "Unavailable",
      "Redirecting number": "+13343822691",
      "Related call ID": "760583469:0",
      "Related reason": "CallQueue",
      "Releasing party": "Remote",
      "Remote call ID": "113103977:0",
      "Remote SessionID": "6bf2f47800105000a0000242be13160a",
      "Report ID": "0a0c2eb7-f1f6-3326-86f9-565d2e11553d",
      "Report time": "2020-05-14T11:01:52.723Z",
      "Route group": "RouteGrpAA",
      "Site main number": "+14692281000",
      "Site timezone": "-300",
      "Site UUID": "474d4f70-4ef5-4d52-9e1d-b207086629e0",
      "Start time": "2020-05-14T11:01:16.545Z",
      "Sub client type": "MOBILE_NETWORK",
      "Transfer related call ID": "2340586843:0A",
      "User": "John Andersen",
      "User number": "+81546668399",
      "User type": "User",
      "User UUID": "47f0d0c2-f05a-44cc-870d-7a3daf859c6c",
      "PSTN Vendor Name": "Cisco Calling Plans",
      "PSTN Legal Entity": "Broadsoft Adaption LLC",
      "PSTN Vendor Org ID": "0b43a1a8-2efd-4892-b301-e7a5a6d2c884",
      "PSTN Provider ID": "e8e730a0-ee04-4df4-90a6-b7072aec9062"
    }
  ]
}

Connect

Support

Developer Community

Developer Events

Contact Sales

Handy Links

Webex Ambassadors

Webex App Hub

Resources

Open Source Bot Starter Kits

Download Webex

DevNet Learning Labs

Terms of Service

Privacy Policy

Cookie Policy

Trademarks

© 2025 Cisco and/or its affiliates. All rights reserved.