Retrieve a person's Monitoring Settings
Retrieves the monitoring settings of the person, which shows specified people, places, virtual lines or call park extenions that are being monitored. Monitors the line status which indicates if a person, place or virtual line is on a call and if a call has been parked on that extension.
This API requires a full, user, or read-only administrator or location administrator auth token with a scope of spark-admin:people_read.
URI Parameters
Unique identifier for the person.
Query Parameters
ID of the organization in which the person resides. Only admin users of another organization (such as partners) may use this parameter as the default is the same organization as the token used to access API.
Response Properties
Call park notification is enabled or disabled.
Settings of monitored elements which can be person, place, virtual line or call park extension.
The identifier of the monitored person.
The last name of the monitored person, place or virtual line.
The first name of the monitored person, place or virtual line.
The display name of the monitored person, place or virtual line.
Indicates whether the type is PEOPLE, PLACE or VIRTUAL_LINE.
Person or list of people.
Place that is not assigned to a specific person such as for a shared device in a common area.
A Virtual line or list of virtual lines.
The email address of the monitored person, place or virtual line.
The list of phone numbers of the monitored person, place or virtual line.
External phone number of the monitored person, workspace or virtual line.
Extension number of the monitored person, workspace or virtual line.
Routing prefix of location.
Routing prefix + extension of a person or workspace.
Indicates whether phone number is a primary number.
The location name where the call park extension is.
The ID for the location.
The identifier of the call park extension.
The name used to describe the call park extension.
The extension number for the call park extension.
The location name where the call park extension is.
The ID for 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
- ID of the organization in which the person resides. Only admin users of another organization (such as partners) may use this parameter as the default is the same organization as the token used to access API.
{
"callParkNotificationEnabled":true,
"monitoredElements":[{
"member": {
"id":"Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85OWNlZjRmYS03YTM5LTQ1ZDItOTNmNi1jNjA5YTRiMjgzODY",
"lastName":"Nelson",
"firstName":"John",
"displayName":"John Nelson",
"type":"PEOPLE",
"email":"john.nelson@gmail.com",
"numbers":[{
"external":"+1-9728138888",
"extension":"1234",
"routingPrefix": "1234",
"esn": "12341234",
"primary":true
}],
"location":"Dallas",
"locationId":"Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzhmZjMwMjg5LWVhMzMtNDc1Ny1iMTBmLWQ2MWIyNzFhMDVlZg"
}},
{"member": {
"id": "Y2lzY29zcGFyazovL3VzL1ZJUlRVQUxfTElORS83MGY2MzYzMC1mZjlmLTExZWItODU5YS0xZjhiYjRjNzc3OGg=",
"lastName": "Smith",
"firstName": "Alice",
"displayName": "AliceSmith",
"type": "VIRTUAL_LINE",
"numbers": [{
"external": "+19075552859",
"extension":"8086",
"routingPrefix": "1234",
"esn": "12341234",
"primary": "true"
}],
"location":"Dallas",
"locationId":"Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzhmZjMwMjg5LWVhMzMtNDc1Ny1iMTBmLWQ2MWIyNzFhMDVlZg"
,
"callparkextension":{
"id":"Y2lzY29zcGFyazovL3VzL0NBTExfUEFSS19FWFRFTlNJT04vZTdlZDdiMDEtN2E4Ni00NDEwLWFlODMtOWJmODMzZGEzNzQy",
"name":"Dallas-Test",
"extension":"4001",
"location":"Dallas",
"locationId":"Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzhmZjMwMjg5LWVhMzMtNDc1Ny1iMTBmLWQ2MWIyNzFhMDVlZg"
}
}}]
}