openapi: 3.2.0
info:
title: 'Webex Reports: Detailed Call History API'
version: 1.0.0
description: 'Operations tagged Reports: Detailed Call History across 2 of this provider''s published API definitions: webex-cloud-calling-openapi.json,
webex-reports-detailed-call-history-api-openapi.yml. Each path carries the servers of the definition it was published
in.'
x-provenance:
method: harvested
authored_by: Cisco Webex
harvested_by: API Evangelist
harvested_on: '2026-08-19'
first_party: true
note: Published by Cisco. Retrieved unmodified except for this x-provenance block.
provider_published: true
derived_view: Per-tag view of webex-cloud-calling-openapi.json, the provider's source document. Operations and schemas
are the provider's, unmodified; only the partition is ours.
derived_from: webex-cloud-calling-openapi.json
operation_coverage: 2/2
x-evidence:
- type: source
url: https://github.com/webex/webex-openapi-specs/blob/main/public-spec/webex-cloud-calling.json
- type: raw
url: https://raw.githubusercontent.com/webex/webex-openapi-specs/main/public-spec/webex-cloud-calling.json
tags:
- name: 'Reports: Detailed Call History'
paths:
/cdr_feed:
get:
responses:
'200':
description: OK
headers:
Link:
schema:
type: string
content:
application/json:
schema:
$ref: '#/components/schemas/CDRResponse'
example:
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
'400':
description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message
will explain further.'
'401':
description: 'Unauthorized: Authentication credentials were missing or incorrect.'
'403':
description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
'404':
description: 'Not Found: The 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.'
'405':
description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
'409':
description: 'Conflict: The 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.'
'410':
description: 'Gone: The requested resource is no longer available.'
'415':
description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used
a media type that is not supported.'
'423':
description: 'Locked: The 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.'
'428':
description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
'429':
description: 'Too Many Requests: Too 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.'
'500':
description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact
the [Webex Developer Support team](/explore/support).'
'502':
description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the
request. Try again later.'
'503':
description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
'504':
description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please
try to reduce it.'
summary: Get Detailed Call History
operationId: getDetailedCallHistory
description: '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`.
<br/><br/>
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.'
tags:
- 'Reports: Detailed Call History'
parameters:
- name: startTime
in: query
description: 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 formatted as `YYYY-MM-DDTHH:MM:SS.mmmZ`.
required: true
example: '2022-06-08T21:27:00.604Z'
schema:
type: string
- name: endTime
in: query
description: 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 formatted as `YYYY-MM-DDTHH:MM:SS.mmmZ`.
required: true
example: '2022-06-09T23:27:18.604Z'
schema:
type: string
- name: locations
in: query
description: 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.
example: Erlanger Urgent / Primary Care Main
schema:
type: string
- name: max
in: query
description: 'Limit the maximum number of reports per page of the response. The range is 500 to 5000. Values below
500 are automatically adjusted up to 500, and values above 5000 are automatically adjusted down to 5000. 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.
For instance, let''s say the initial API request is
https://analytics-calling.webexapis.com/v1/cdr_feed?endTime=2025-08-15T10:00:00.000Z&startTime=2025-08-15T08:00:00.000Z&max=5000
The link header in the response would look something like
<<https://analytics-calling.webexapis.com/v1/cdr_feed?endTime=2025-08-15T10:00:00.000Z&startTime=2025-08-15T08:00:00.000Z&startTimeForNextFetch=2025-08-15T09:30:00.000Z&totalCount=20000&max=5000&orgId=zzzzzzzz-yyyy-zzzz-xxxx-yyyyyyyyyyyy>;rel="next">'
example: 1000
schema:
type: number
default: 5000
/cdr_stream:
get:
responses:
'200':
description: OK
headers:
Link:
schema:
type: string
content:
application/json:
schema:
$ref: '#/components/schemas/CDRResponse'
example:
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
'400':
description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message
will explain further.'
'401':
description: 'Unauthorized: Authentication credentials were missing or incorrect.'
'403':
description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
'404':
description: 'Not Found: The 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.'
'405':
description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
'409':
description: 'Conflict: The 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.'
'410':
description: 'Gone: The requested resource is no longer available.'
'415':
description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used
a media type that is not supported.'
'423':
description: 'Locked: The 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.'
'428':
description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
'429':
description: 'Too Many Requests: Too 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.'
'500':
description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact
the [Webex Developer Support team](/explore/support).'
'502':
description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the
request. Try again later.'
'503':
description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
'504':
description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please
try to reduce it.'
summary: Get Live Stream Detailed Call History
operationId: getLiveStreamDetailedCallHistory
description: '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 time window during which Detailed Call History data was inserted into the Webex Calling cloud.
The API will return all reports whose insertion time into the Webex Calling cloud falls between `startTime` and `endTime`.
<br/><br/>
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.'
tags:
- 'Reports: Detailed Call History'
parameters:
- name: startTime
in: query
description: The start date-time of the first record you wish to collect in UTC time. It would be the earliest time
at which the data was inserted into the Webex Calling cloud for the records you wish to collect. Format must be
as `YYYY-MM-DDTHH:MM:SS.mmmZ`. `startTime` can't be older than 12 hours from your current UTC time. The window period
between `startTime` and `endTime` must not exceed 2 hours in a single API request.
required: true
example: '2022-06-08T21:27:00.604Z'
schema:
type: string
- name: endTime
in: query
description: The end date-time of the last record you wish to collect in UTC time. It would be the latest time at
which the data was inserted into the Webex Calling cloud for the records you wish to collect. Format must be as
`YYYY-MM-DDTHH:MM:SS.mmmZ`. `endTime` must be 1 minute ago from your current UTC time and can’t be older than 12
hours. `endTime` must be greater than `startTime`. The window period between `startTime` and `endTime` must not
exceed 2 hours in a single API request.
required: true
example: '2022-06-09T23:27:18.604Z'
schema:
type: string
- name: locations
in: query
description: 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.
example: Erlanger Urgent / Primary Care Main
schema:
type: string
- name: max
in: query
description: 'Limit the maximum number of reports per page of the response. The range is 500 to 5000. Values below
500 are automatically adjusted up to 500, and values above 5000 are automatically adjusted down to 5000. 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.
For instance, let''s say the initial API request is
https://analytics-calling.webexapis.com/v1/cdr_stream?endTime=2025-08-15T10:00:00.000Z&startTime=2025-08-15T08:00:00.000Z&max=5000
The link header in the response would look something like
<<https://analytics-calling.webexapis.com/v1/cdr_stream?endTime=2025-08-15T10:00:00.000Z&startTime=2025-08-15T08:00:00.000Z&startTimeForNextFetch=2025-08-15T09:30:00.000Z&totalCount=20000&max=5000&orgId=zzzzzzzz-yyyy-zzzz-xxxx-yyyyyyyyyyyy>;rel="next">'
example: 1000
schema:
type: number
default: 5000
components:
schemas:
CDRResponse:
type: object
properties:
items:
type: array
description: Array of detailed call history records
items:
$ref: '#/components/schemas/CDR'
example:
items:
- Report ID: 0a0c2eb7-f1f6-3326-86f9-565d2e11553d
Report time: '2020-05-14T11:01:52.723Z'
Call ID: SSE1101163211405201218829100@10.177.4.29
User: John Andersen
Duration: 36
CDR:
type: object
properties:
Answer indicator:
type: string
example: 'Yes'
description: "Whether the call leg was answered after a redirection. Possible values: \n\n- Yes\n\n- No\n\n- Yes-PostRedirection"
Answer time:
type: string
example: '2020-05-14T11:01:17.551Z'
description: The time the call was answered. Time is in UTC.
Answered:
type: string
example: 'true'
description: 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:
type: string
example: '107'
description: 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:
type: string
example: SSE1101163211405201218829100@10.177.4.29
description: 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:
type: string
example: '2003'
description: '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:
type: string
example: Success
description: '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:
type: string
example: Normal
description: "Additional information about the Call outcome returned. Possible reasons are:\n\n- Success\n - Normal:\
\ Call is completed successfully.\n - UserBusy: Call is a success, but the user is busy.\n - NoAnswer: Call\
\ is a success, but the user didn't answer.\n\n- Refusal\n - CallRejected: Call attempt rejected at the recipient's\
\ end.\n - UnassignedNumber: The dialed number isn't assigned to any user or service.\n - SIP408: Request timed\
\ out because couldn’t find the user in time.\n - InternalRequestTimeout: Request timed out as the service couldn’t\
\ fulfill the request due to an unexpected condition.\n - Q850102ServerTimeout: Recovery on timer expiry/server\
\ timed out\n - NoUserResponse: No response from any end-user device/client\n - NoAnswerFromUser: No answer\
\ from the user.\n - SIP480: Callee or called party is currently unavailable.\n - SIP487: Request is terminated\
\ by bye or cancel.\n - TemporarilyUnavailable: User is temporarily unavailable.\n - AdminCallBlock: Call attempt\
\ is rejected due to the organization's call block list.\n - UserCallBlock: The call to user is rejected because\
\ the number is on the user's block list.\n - Unreachable: Unable to route the call to the desired destination.\n\
\ - LocalGatewayLoop: Loop detected between the local gateway and Webex Calling.\n - UserAbsent: User is temporarily\
\ unreachable or unavailable.\n\n- Failure\n - DestinationOutOfOrder: Service request failed as the destination\
\ can’t be reached or the interface to the destination isn’t functioning correctly.\n - SIP501: Invalid method\
\ and can’t identify the request method.\n - SIP503: Service is temporarily unavailable so can’t process the\
\ request.\n - ProtocolError: Unknown or unimplemented release code.\n - SIP606: Some aspect of the session\
\ description wasn't acceptable.\n - NoRouteToDestination: No route available to the destination\n - Internal:\
\ Failed because of internal Webex Calling reasons.\n - MaxConcurrentTerminatingAlertingRequestsExceeded: The\
\ number of simultaneous unanswered calls to a local gateway, for the same calling and called number, exceeded\
\ the limit.\n - RouteListCalls: When off-net route list call is blocked due to exceeding the Route List Calls\
\ license overage limit for the organization."
Call Recording Platform Name:
type: string
example: Webex
description: '`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:
type: string
example: successful
description: 'Status of the recorded media: "successful", "failed", or "successful but not kept." '
Call Recording Trigger:
type: string
example: always
description: '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:
type: string
example: '2023-06-05T18:21:29.707Z'
description: 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:
type: string
example: SIP_ENTERPRISE
description: '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:
type: string
example: CALLEDCLIDGOESHERE
description: 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:
type: string
example: '2002'
description: For incoming calls, the telephone number of the user. For outgoing calls, it's the telephone number
of the called party.
Calling line ID:
type: string
example: YOURCLIDGOESHERE
description: 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:
type: string
example: '2001'
description: For incoming calls, the telephone number of the calling party. For outgoing calls, it's the telephone
number of the user.
Client type:
type: string
example: SIP_TOLLFREE
description: '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:
type: string
example: 1.0.2.3
description: The version of the client that the user (creating this record) is using to make or receive the call.
Correlation ID:
type: string
example: 8e8e1dc7-4f25-4595-b9c7-26237f824535
description: Correlation ID to tie together multiple call legs of the same call session.
Department ID:
type: string
example: 4370c763-81ec-403b-aba3-626a7b1cf264
description: A unique identifier for the user's department name.
Device MAC:
type: string
example: 6C710D8ABC10
description: The MAC address of the device, if known.
Device owner UUID:
type: string
example: 1e9e14c7-4f25-4595-b9c7-26237f824536
description: "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. \n\n- Only set when the device owner is different than the owner of the device who made/received\
\ the call."
Dialed digits:
type: string
example: '1246'
description: "The keypad digits as dialed by the user, before pre-translations. \nThis field reports multiple call\
\ dial possibilities:\n\n- Feature access codes (FAC) used for invoking features such as Last Number Redial or\
\ a Call Return.\n\n- An extension that got dialed and a mis-dialed keypad digit from a device/app.\n\n- 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. \nNote that when pre-translations have no effect, the dialed\
\ digits field contains the same data as the called number field. \nThis field is only used for originating (outgoing)\
\ Calls and is not available for terminating (incoming) Calls."
Direction:
type: string
example: ORIGINATING
description: 'Whether the call was inbound or outbound. The possible values are:
- ORIGINATING
- TERMINATING'
Duration:
type: number
example: 36
description: The length of the call in seconds.
External caller ID number:
type: string
example: '2004'
description: "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. \n\n- Only included in originating\
\ CDRs (not present in terminating CDRs).\n\n- Not set for calls that are redirected"
Final local SessionID:
type: string
example: 82bb753300105000a0000242be131609
description: '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 Id
# --- truncated at 32 KB (102 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/webex/refs/heads/main/openapi/webex-reports-detailed-call-history-api-openapi.yml