Get a Wholesale Customer
This API will allow a Service Provider to retrieve details of a provisioned Wholesale customer on Cisco Webex.
URI Parameters
A unique identifier for the customer in question.
Response Properties
A unique Cisco identifier for the customer.
The Organization ID of the enterprise on Cisco Webex, to be used when referencing this customer on other Cisco Webex APIs. Only presented when status is provisioned.
External Id of the Customer.
addressLine1
addressLine2
City of the customer
State or Province of the customer
Postal/Zip code of the customer
ISO2 country code of the customer size = 2
The provisioning status of the customer.
The customer is fully provisioned on Cisco Webex.
The customer is provisioned with errors.
The customer is provisioning.
The customer is updating.
The customer is being deleted.
An error occurred provisioning the customer on Cisco Webex.
List of package names provisioned
The Webex Wholesale Packages assigned to the customer.
The Webex Common Area Calling Package
The Webex Calling Package
The Webex Meetings Package
The Webex Suite Package
The provisioning status of the a particular package.
The customer is fully provisioned on Cisco Webex.
The customer is provisioning.
The customer is being deleted.
An error occurred provisioning the customer on Cisco Webex.
List of warnings that occurred during that last attempt to provision/update this customer.
Note:
This list captures errors that occurred during asynchronous or background provisioning of the customer, after the API has been accepted and 202 response returned.
Any errors that occur during initial API request validation will be captured directly in error response with appropriate HTTP status code.
An error code that identifies the reason for the error
A textual representation of the error code.
List of errors that occurred during that last attempt to provision/update this customer.
Note:
This list captures errors that occurred during asynchronous or background provisioning of the customer, after the API has been accepted and 202 response returned.
Any errors that occur during initial API request validation will be captured directly in error response with appropriate HTTP status code.
An error code that identifies the reason for the error
A textual representation of the error code.
List of errors that occurred during that last attempt to provision/update this customer.
Note:
This list captures errors that occurred during asynchronous or background provisioning of the customer, after the API has been accepted and 202 response returned.
Any errors that occur during initial API request validation will be captured directly in error response with appropriate HTTP status code.
An error code that identifies the reason for the error
A textual representation of the error code.
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. |
| 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
{
"id": "Y2lzY29zcGFyazovL3VzL0VOVEVSUFJJU0UvNTJjZjU3NmQtNjBhOC00MDdhLWIyMmMtNDY3YzUxNTkxOTA4",
"orgId": "Y2lzY29zcGFyazovL3VzL09yZ2FuaXphdGlvbi81MmNmNTc2ZC02MGE4LTQwN2EtYjIyYy00NjdjNTE1OTE5MDk",
"externalId": "c1677a16-557a-4fb4-b48f-24adde57ec99",
"address" :{
"addressLine1": "771 Alder Drive",
"addressLine2": "Cisco Site 5",
"city": "Milpitas",
"stateOrProvince": "CA",
"zipOrPostalCode": "95035",
"country": "US"
},
"status": "provisioned",
"packages": [
"webex_calling"
],
"resourceDetails":
{
"packages": [
{
"name": "webex_calling",
"status": "provisioned",
"warnings": [
{
"errorCode": 2526,
"description": "The requested operation did not successfully provision numbers for the Webex Calling Location"
},
{
"errorCode": 2527,
"description": "The requested operation did not successfully assign a main number to the Webex Calling Location"
}
]
}
]
}
}