Get the job status of Update Routing Prefix job
Get the status of the update routing prefix job by its job ID.
The routing prefix is associated with a location and is used to route calls belonging to that location. This API allows users to check the status of update routing prefix job by job ID in an organization.
Checking the status of the update routing prefix job in an organization requires a full, user, or read-only administrator auth token with a scope of spark-admin:telephony_config_read.
URI Parameters
Retrieve job status for this jobId.
Query Parameters
Check update routing prefix job status in this organization.
Response Properties
Job name.
Unique identifier of the job.
Unique identifier to track the flow of HTTP requests.
Unique identifier to identify which user has run the job.
Unique identifier to identify the customer who has run the job.
Unique identifier to identify the customer for which the job was run.
Unique identifier to identify the instance of the job.
Displays the most recent step's execution status. Contains execution statuses of all the steps involved in the execution of the job.
Unique identifier that identifies each instance of the job.
Job execution start time in UTC format.
Job execution end time in UTC format.
Last updated time (in UTC format) post one of the step execution completion.
Displays status for overall steps that are part of the job.
Exit Code for a job.
Job creation time in UTC format.
Status of each step within a job.
Unique identifier that identifies each step in a job.
Step execution start time in UTC format.
Step execution end time in UTC format.
Last updated time for a step in UTC format.
Displays status for a step.
Exit Code for a step.
Step name.
Time lapsed since the step execution started.
Indicates the most recent status (STARTING, STARTED, COMPLETED, FAILED) of the job at the time of invocation.
Most recent exit code of the job at the time of invocation.
Job is in progress.
Job has completed successfully.
Job has failed.
Job has been stopped.
Job has completed with errors.
Job statistics.
Indicates the total number of records whose routing prefix update is successful.
Indicates the total number of records whose routing prefix update failed.
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
- Check update routing prefix job status in this organization.
{
"name": "updateroutingprefix",
"id": "Y2lzY29zcGFyazovL3VzL0pPQl9JRC81YWE1NWZjNC1lNTYwLTQ3MWQtOGZhZS0yNDc3NDM3MDNkNmI",
"trackingId": "NA_e82bec92-7a6c-48e5-9511-bfe4da78396e",
"sourceUserId": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS85OThhMThhYi1kZjY5LTQ5MWYtYmViZi03MzUxMGE3ODI5N2I",
"sourceCustomerId": "Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE",
"targetCustomerId": "Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE",
"instanceId": 1,
"jobExecutionStatus": [
{
"id": 1,
"startTime": "2023-08-16T18:30:20.901Z",
"endTime": "2023-08-16T18:30:34.793Z",
"lastUpdated": "2023-08-16T18:30:36.631Z",
"statusMessage": "COMPLETED",
"exitCode": "COMPLETED",
"createdTime": "2023-08-16T18:30:20.882Z",
"stepExecutionStatuses": [
{
"id": 2,
"startTime": "2023-08-16T18:30:20.970Z",
"endTime": "2023-08-16T18:30:22.801Z",
"lastUpdated": "2023-08-16T18:30:22.801Z",
"statusMessage": "COMPLETED",
"exitCode": "COMPLETED",
"name": "updateroutingprefixPreProcessMemberData",
"timeElapsed": "PT1.831S"
},
{
"id": 3,
"startTime": "2023-08-16T18:30:22.811Z",
"endTime": "2023-08-16T18:30:26.022Z",
"lastUpdated": "2023-08-16T18:30:26.022Z",
"statusMessage": "COMPLETED",
"exitCode": "COMPLETED",
"name": "updateroutingprefixGenerateUserReport",
"timeElapsed": "PT3.211S"
},
{
"id": 4,
"startTime": "2023-08-16T18:30:26.032Z",
"endTime": "2023-08-16T18:30:26.538Z",
"lastUpdated": "2023-08-16T18:30:26.538Z",
"statusMessage": "COMPLETED",
"exitCode": "COMPLETED",
"name": "updateroutingprefixPreProcessCiUserData",
"timeElapsed": "PT0.506S"
},
{
"id": 5,
"startTime": "2023-08-16T18:30:26.549Z",
"endTime": "2023-08-16T18:30:29.907Z",
"lastUpdated": "2023-08-16T18:30:29.907Z",
"statusMessage": "COMPLETED",
"exitCode": "COMPLETED",
"name": "updateroutingprefixGenerateMachineAccountReport",
"timeElapsed": "PT3.358S"
},
{
"id": 6,
"startTime": "2023-08-16T18:30:29.916Z",
"endTime": "2023-08-16T18:30:30.007Z",
"lastUpdated": "2023-08-16T18:30:30.007Z",
"statusMessage": "COMPLETED",
"exitCode": "COMPLETED",
"name": "updateroutingprefixPreProcessCiMachineAccountData",
"timeElapsed": "PT0.091S"
},
{
"id": 7,
"startTime": "2023-08-16T18:30:30.018Z",
"endTime": "2023-08-16T18:30:34.447Z",
"lastUpdated": "2023-08-16T18:30:34.447Z",
"statusMessage": "COMPLETED",
"exitCode": "COMPLETED",
"name": "updateroutingprefixFetchVONExtensions",
"timeElapsed": "PT4.429S"
},
{
"id": 8,
"startTime": "2023-08-16T18:30:34.466Z",
"endTime": "2023-08-16T18:30:34.789Z",
"lastUpdated": "2023-08-16T18:30:34.789Z",
"statusMessage": "COMPLETED",
"exitCode": "COMPLETED",
"name": "updateroutingprefixUpdateRoutingPrefix",
"timeElapsed": "PT0.323S"
}
],
"timeElapsed": "PT13.749S"
}
],
"latestExecutionStatus": "COMPLETED",
"latestExecutionExitCode": "COMPLETED",
"counts": {
"routingPrefixFailed": 0,
"routingPrefixUpdated": 7
}
}