Get Details for a Call Park
Retrieve Call Park details.
Call Park allows call recipients to place a call on hold so that it can be retrieved from another device.
Retrieving call park details requires a full or read-only administrator or location administrator auth token with a scope of spark-admin:telephony_config_read
.
NOTE: The Call Park ID will change upon modification of the Call Park name.
URI Parameters
Retrieve settings for a call park in this location.
Retrieve settings for a call park with the matching ID.
Query Parameters
Retrieve call park settings from this organization.
Response Properties
A unique identifier for the call park.
Unique name for the call park. The maximum length is 80.
Recall options that are added to call park.
Alternate user which is a hunt group ID for call park recall alternate destination.
Unique name for the hunt group.
Call park recall options.
Alert parking user only.
Alert parking user first, then hunt group.
Alert hunt group only.
People, workspaces and virtual lines that are eligible to receive calls.
ID of a person, workspace or virtual line.
First name of a person, workspace or virtual line.
Last name of a person, workspace or virtual line.
Display name of a person, workspace or virtual line.
Type of the person, workspace or virtual line.
Indicates that this object is a user.
Indicates that this object is a place.
Indicates that this object is a virtual line.
Email of a person or workspace.
List of phone numbers of a person, workspace or virtual line.
Phone number of a person or workspace.
Extension of a person or workspace.
Routing prefix of location.
Routing prefix + extension of a person or workspace.
Flag to indicate a primary phone.
Whether or not the calls will be parked on agents as a destination.
Array of call park extensions assigned to a call park.
Unique identifier for the call park extension.
The extension for the call park.
A unique name for the call park extension.
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
- orgIdstringRetrieve call park settings from this organization.
{ "id": "Y2lzY29zcGFyazovL3VzL0NBTExfUEFSSy9kR1ZqYUc1cFkyRnNJSE4xY0hCdmNuUWdMU0JwYm5OMWNtRnVZMlVnTFNCamRYTjBiMjFsY2lBeA==", "name": "technical support - insurance - customer 1", "recall": { "huntGroupId": "Y2lzY29zcGFyazovL3VzL0hVTlRfR1JPVVAvZEdWamFHNXBZMkZzTFhOMWNIQnZjblF0TlRVMU9EWTNOVE13T1VCbmJXRnBiQzVqYjIwPQ", "huntGroupName": "Technical Support Group - 5558675309", "option": "ALERT_PARKING_USER_FIRST_THEN_HUNT_GROUP" }, "agents": [ { "id": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS80NDVkMzMzMC1mNjE3LTExZWItOWQyZS01NzViODE3ZGE2NmE", "firstName": "John", "lastName": "Brown", "displayName": "John Brown", "type": "PEOPLE", "email": "john.brown@example.com", "numbers": [ { "external": "+19075552859", "extension":"8080", "routingPrefix": "1234", "esn": "12348080", "primary": "true" } ] }, { "id": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS83MGY2MzYzMC1mZjlmLTExZWItODU5YS0xZjhiYjRjNzc1MWQ", "firstName": "John", "lastName": "Smith", "displayName": "John Smith", "type": "PEOPLE", "email": "john.smith@example.com", "numbers": [ { "external": "+19075553859", "extension":"8081", "routingPrefix": "1234", "esn": "12348081", "primary": "true" } ] } ], "parkOnAgentsEnabled": false, "callParkExtensions": [ { "id": "Y3lzY29zcGFyazovL3VzL1BFT1BMRS83MGY2MzYzMC1mZjlmLTExZWItODU5YS0xZjhiYjRjNzc2MWQ", "extension":"1415", "name": "14159265" } ] }