Get Recording Details
Retrieves details for a recording with a specified recording ID.
Only recordings of owner with the authenticated user may be retrieved.
Get Recording Details requires the spark-compliance:recordings_read scope.
Request Header
timezone: Time zone in conformance with the IANA time zone database. The default is UTC iftimezoneis not defined.
URI Parameters
A unique identifier for the recording.
Response Properties
A unique identifier for recording.
The recording's topic.
The date and time recording was created in ISO 8601 compliant format. Please note that it's not the time the record button was clicked in meeting but the time the recording file was generated offline.
The date and time recording started in ISO 8601 compliant format. It indicates when the record button was clicked in the meeting.
Recording file format is MP3.
Recording service-type is calling.
The duration of the recording in seconds.
The size of the recording file in bytes.
The download links for MP3, audio of the recording without HTML page rendering in browser or HTTP redirect. This attribute is not available if the user is not a Compliance Officer and Prevent Downloading has been turned on for the recording being requested. The Prevent Downloading option can be viewed and set on page when editing a recording. Note that there are various products in Webex Suite such as "Webex Meetings", "Webex Training" and "Webex Events".
The download link for recording audio file without HTML page rendering in browser or HTTP redirect. Expires 3 hours after the API request.
The download link for recording transcript file without HTML page rendering in browser or HTTP redirect. Expires 3 hours after the API request.
The date and time when recordingDownloadLink, audioDownloadLink, and transcriptDownloadLink expire in ISO 8601 compliant format.
Recording is available.
Recording has been moved to the recycle bin.
Webex UUID for recording owner/host.
Webex email for recording owner/host.
Recording belongs to a user.
Recording belongs to a workspace device.
Recording belongs to a workspace device.
Storage location for recording within Webex datacenters.
Fields relevant to each service Type.
Webex calling location for recording user.
Call ID for which recording was done.
Response Codes
The list below describes the common success and error responses you should expect from the API:
| Code | Status | Description |
|---|---|---|
| 200 | OK | Successful request with body content. |
| 201 | Created | The request has succeeded and has led to the creation of a resource. |
| 202 | Accepted | The request has been accepted for processing. |
| 204 | No Content | Successful request without body content. |
| 400 | Bad Request | The request was invalid or cannot be otherwise served. An accompanying error message will explain further. |
| 401 | Unauthorized | Authentication credentials were missing or incorrect. |
| 403 | Forbidden | The request is understood, but it has been refused or access is not allowed. |
| 404 | 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 | Method Not Allowed | The request was made to a resource using an HTTP request method that is not supported. |
| 409 | 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 | Gone | The requested resource is no longer available. |
| 415 | 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 | 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 | Precondition Required | File(s) cannot be scanned for malware and need to be force downloaded. |
| 429 | 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 | Internal Server Error | Something went wrong on the server. If the issue persists, feel free to contact the Webex Developer Support team. |
| 502 | Bad Gateway | The server received an invalid response from an upstream server while processing the request. Try again later. |
| 503 | Service Unavailable | Server is overloaded with requests. Try again later. |
| 504 | Gateway Timeout | An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it. |
Header
{
"id": "62807eaf-0c89-492e-a3c3-c4751812603b",
"topic": "call with default",
"createTime": "2023-11-01T23:09:05+08:00",
"timeRecorded": "2023-11-01T15:27:29+08:00",
"temporaryDirectDownloadLinks": {
"audioDownloadLink": "https://nsq1wss.dmz.webex.com/nbr/MultiThreadDownloadServlet?type=calling&orgId=59e67527-4651-4c90-b2f0-4f86c3bb6608&recordUUID=62807eaf-0c89-492e-a3c3-c4751812603b&ticket=SDJTSwAAAIV9%2BooFzh%2FkPd1Edek7wtCLYrVcjsJ2RTHGbhwYHpWOEQ%3D%3D×tamp=1699495025258",
"expiration": "2023-11-09T12:57:05Z"
},
"ownerId": "24683d6c-5529-4b60-a6c7-91e8b293bbab",
"ownerType": "user",
"ownerEmail": "nshtestwebex+crctestuser1@gmail.com",
"format": "MP3",
"durationSeconds": 298,
"sizeBytes": 299918,
"serviceType": "calling",
"storageRegion": "US",
"status": "available",
"serviceData": {
"locationId": "02a43ee9-17ae-4e0c-9e79-720e3a6503fd",
"callSessionId": "c61b357e-8f53-4d97-9cd2-ae3202796fb0"
}
}