Get a Location Emergency callback number
Get location emergency callback number.
- To retrieve location callback number requires a full, user or read-only administrator or location administrator auth token with a scope of
spark-admin:telephony_config_read.
URI Parameters
Update location attributes for this location.
Query Parameters
Update location attributes for this organization.
Response Properties
Data relevant to this location.
The location DN.
The name of the location.
The source from which the emergency calling line ID (CLID) is selected for an actual emergency call, applying fallback rules as necessary.
Location TN.
Assigned number of a user or workspace in the location.
Location calling line ID (CLID) number. Avaliable only when number is present and quality would be invalid.
Used to represent whether a number is a recommended ECBN.
Data relevant to the user/place (member) selected for ECBN.
The member DN.
The member first name.
The member last name. Always contains . if the member is a place.
Member ID of user/place within the location.
Member Type.
The source from which the emergency calling line ID (CLID) is selected for an actual emergency call, applying fallback rules as necessary.
Location TN.
Assigned number of a user or workspace in the location.
Location CLID number. Avaliable only when number is present and quality would be invalid.
Used to represent whether a number is a recommended ECBN.
Selected number type to configure emergency call back.
Location TN.
Assigned number of a user or workspace in the location.
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
- Update location attributes for this organization.
{
"locationInfo": {
"phoneNumber": "+12145551767",
"name": "CPAPI_Dev_Test_Location_DND",
"effectiveLevel": "LOCATION_NUMBER",
"effectiveValue": "+12145551767",
"quality": "RECOMMENDED"
},
"locationMemberInfo": {
"phoneNumber": "+12145551767",
"firstName": "cpapiandhydra",
"lastName": "cpapiandhydra@gmail.com",
"memberId": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS82MmQ3YTY3MS00YmVlLTQ2MDItOGVkOC1jOTFmNjU5NjcxZGI",
"memberType": "PEOPLE",
"effectiveLevel": "LOCATION_MEMBER_NUMBER",
"effectiveValue": "+12145551767",
"quality": "RECOMMENDED"
},
"selected": "LOCATION_MEMBER_NUMBER"
}