Precheck a Wholesale Customer Provisioning
This API will allow the Partner sales team to verify likely success of provisioning a Wholesale customer.
packages Note:
cisco_calling_planis dependent on:common_area_calling,webex_calling,webex_suite,webex_voice,cx_essentials
The Prerequisite for using this API is to have wxc-wholesale entitlement or webex-wholesale-partner-testing setting enabled for the Partner Organization. The Provisioning Precheck APIs supports two variants of Wholesale Customer Provisioning Precheck Requests. Please refer to Using the Provisioning Precheck APIs section in Webex for Wholesale guide for more information.
Query Parameters
The encoded organization ID for the sub partner.
Body Parameters
This Provisioning ID defines how this wholesale customer is to be provisioned for Cisco Webex Services.
Each Customer Template will have its unique Provisioning ID. This ID will be displayed under the chosen Customer Template on Cisco Webex Control Hub.
The complete list of Webex Wholesale packages to be assigned to the Wholesale customer.
The organization ID of the enterprise in Cisco Webex.
External ID of the Wholesale customer.
Billing address of the Wholesale customer.
AddressLine1.
AddressLine2.
City of the Wholesale customer.
State or Province of the Wholesale customer. This attribute may be required in specific geographies. Please refer to Wholesale Customer Address Requirement for more information.
Postal/Zip code of the Wholesale customer. This attribute may be required in specific geographies. Please refer to Wholesale Customer Address Requirement for more information.
ISO2 country code of the Wholesale customer size = 2.
The name of the Wholesale customer.
The primary email address of the Wholesale customer.
Name of the wholesale customer office.
Address of the wholesale customer.
State or Province of the Wholesale customer. This attribute may be required in specific geographies. Please refer to Wholesale Customer Address Requirement for more information.
Postal/Zip code of the Wholesale customer. This attribute may be required in specific geographies. Please refer to Wholesale Customer Address Requirement for more information.
Customer timezone for calling package. The full list of supported timezones can be found at List of Time Zones for Wholesale Provisioning.
Determine language for all generated emails and voice announcements.
SIP Header for any emergency calls from this location.
Wholesale Customer timezone for meetings package.
Response Properties
A textual representation of the Precheck response message containing the infoCode object in the case of a success response and the errorCode object in the case of failure.
A list of ProvisioningPreCheckResponseInfo object.
Provisioning Precheck infoCode.
A textual description of the infoCode.
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
- The encoded organization ID for the sub partner.
Body
- This Provisioning ID defines how this wholesale customer is to be provisioned for Cisco Webex Services. Each Customer Template will have its unique Provisioning ID. This ID will be displayed under the chosen Customer Template on Cisco Webex Control Hub.
- The complete list of Webex Wholesale packages to be assigned to the Wholesale customer.
- The organization ID of the enterprise in Cisco Webex.
- External ID of the Wholesale customer.
- Billing address of the Wholesale customer.
{
"address": {
"addressLine1": "771 Alder Drive",
"addressLine2": "Cisco Site 5",
"city": "Milpitas",
"stateOrProvince": "CA",
"zipOrPostalCode": "95035",
"country": "US"
},
"customerInfo": {
"primaryEmail": "john.anderson@acme.com"
}
}
{
"message": "success",
"info": [
{
"infoCode": 100,
"description": "Provisioning preCheck validation successful."
}
]
}