Get Job Errors for a Call Recording Job
Get errors for a call recording job in an organization.
The Call Recording feature supports multiple third-party call recording providers, or vendors, to capture and manage call recordings. An organization is configured with an overall provider, but locations can be configured to use a different vendor than the overall organization default.
Requires a full or read-only administrator auth token with a scope of spark-admin:telephony_config_read.
URI Parameters
Retrieve job errors for this job.
Query Parameters
Retrieve job errors for a call recording job in this organization.
Limit the number of errors returned to this maximum count. The default is 50.
Response Properties
List of errors with details.
Index of error number.
Unique identifier (UUID) of the error.
Contains error details.
HTTP error code.
Message string with further error information.
Error message.
Error messages describing the location ID in which the error occurs. For a move operation, this is the target location ID.
Unique tracking ID of the request.
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
Query Parameters
- Retrieve job errors for a call recording job in this organization.
- Limit the number of errors returned to this maximum count. The default is 50.
{
"items": [
{
"itemNumber": 0,
"item": "5d320be1-e28c-420a-8935-1a54c7826eb4",
"error": {
"key": "500",
"message": [
{
"description": "POST failed: HTTP/1.1 404 Not Found",
"code": null,
"locationId": null
}
]
},
"trackingId": "ADMINBATCHCLIENT_2830be24-766e-4a2a-be36-d289eb890322_0_3"
}
]
}