APIs
XML API DeprecationGetting StartedREST API BasicsComplianceWebhooksWebex APIs
Admin
Calling
Devices
Meetings
Messaging
Webex Assistant Skills
FedRAMP
Full API Reference
API Changelog

Webex for Wholesale

Cisco Webex for Wholesale is an offer that allows Partners to use the Webex Suite as a Package based Utility Model. Learn how to use the Webex for Wholesale Provisioning APIs.

anchorWhat's possible with Webex for Wholesale Provisioning APIs
anchor

The Webex for Wholesale Provisioning API is for the Service Providers (SPs) who sign up for Cisco Webex for Wholesale. The API enables those SPs to provision, update, and remove wholesale customer/subscribers.

Wholesale Customer Provisioning APIs

Wholesale Subscriber Provisioning APIs

anchorUsing the Provisioning API
anchor

The Webex for Wholesale Provisioning API is for Service Providers (SPs) who sign up for Cisco Webex for Wholesale. The API enables those SPs to provision, update, and remove Cisco Webex services for their customers and subscribers.

anchorMethods and Content Types
anchor

The Webex for Wholesale Provisioning Public API is RESTful. In REST, a base URL represents each resource. You use the HTTP methods GET, POST and DELETE to request data and perform actions on those resources.

For methods that accept request parameters, the platform accepts only application/json content types.

anchorWholesale Customer Address Requirement
anchor

The billing address and calling address of the customer should be provided per the below guidelines:

AttributeMandatory
addressLine1Yes
addressLine2No
cityYes
stateOrProvinceMandatory for some geographic locations.
zipOrPostalCodeMandatory for some geographic locations.
countryYes
anchorWhat's possible with Webex for Wholesale Billing Reports Public APIs
anchor

The Wholesale Billing Reports Public APIs are a set of APIs that are targeted at Service Providers who sign up to the Webex for Wholesale solution. These APIs provides partner, customer and user breakdown reports to the Service Providers or Partners. Service Providers can use these reports to reconcile their monthly invoice.

The Webex for Wholesale Billing Reports Public API is RESTful. In REST, a base URL represents each resource. You use the HTTP methods GET, POST and DELETE to request data and perform actions on those resources.

anchorAPI Error Codes
anchor

These APIs return standard HTTP status codes for request responses. For more information on standard HTTP status codes, please see Webex REST API Basics.

The following error codes may appear in API Error responses, or included in responses to Wholesale Get/Create/List API requests. These are complementary to the overall HTTP Status codes and provide additional clarity on the reason for the error.

Error CodeDetailHTTP Status CodePossible in Subscriber response?
1001Invalid Mandatory Parameter
A mandatory parameter has not been specified in the API request.

400No
1002Invalid Parameter Size
A parameter in the API request is outside the bounds of expected size.

400No
1003Invalid Parameter Format
A parameter in the API request is not correctly formatted.

Common Causes:
  • A required parameter is not provided.
  • A parameter is not provided in the required format.
Possible Solutions:
    Please follow the respective API docs in Wholesale Organization Provisioning APIs or Wholesale Subscriber Provisioning APIs section.
400No
1004Invalid Query Parameter
The query parameter specified in Subscriber or Customer Search/List API request is invalid.

Common Causes:
  • The email query parameter is not in valid email address format. The specification of a valid email can be found in RFC 2822.
  • The personId query parameter is not valid.
  • The customerId query parameter is not valid.
  • The externalCustomerId query parameter is not valid.
400No
1005Invalid or Bad HTTP request
The HTTP request message specified is either bad or invalid.

Common Causes:
  • The HTTP request message has a typographical error
  • The HTTP request message is missing a required header e.g. Content-Length
Refer to RFC 2616 Hypertext Transfer Protocol for more details.
400No
2001Subscriber Not Found
The subscriberId specified in an API Request to Get, Update, Delete a Subscriber could not be found.

Common Causes:
  • The subscriber in question was previously deleted.
  • The subscriberId specified is invalid.
404No
2002Subscriber pre-exists in another Cisco Webex wholesale organization
The subscriber has previously mapped to a new or existing webex wholesale organization. However, the email address associated with this subscriber has been found in a different webex wholesale organization. Cisco cannot automatically move this subscriber to the desired organization and so provisioning fails.

Common Causes:
  • The subscriber in question already has free or paid webex wholesale services using this email address in another webex wholesale organization.
  • The email address supplied is incorrect.

Possible Solutions:
  1. Validate that the supplied email is correct.
  2. Confirm with the customer/subscriber that their enterprise has been mapped to the correct webex wholesale organization.
  3. Work with the customer/subscriber to close their existing Cisco Webex account or change the email address associated with that account.
  4. Supply an alternate email address for the subscriber.
409Yes
2003Subscriber Update Not Allowed
The subscriber update operation is not allowed because of the current provisioning status of the subscriber.

Common Causes:
  • Subscriber Provisioning/Update is currently in progress - subscriber status is provisioning or updating.
  • Subscriber provisioning had previously failed and the subscriber status is error.

Possible Solutions:
  1. Check current Subscriber Status.
  2. If Subscriber Provisioning is in progress, wait until status transitions to a final status of (provisioned or error) before proceeding with appropriate next step.
  3. If subscriber is in error status, you will need to send a new Provision Subscriber API request instead to re-provision the subscriber.
403No
2005Package Type Not Supported
The package type specified in the Provision/Update request is not supported.
Note: This only applies where the associated Customer Template is configured with Automatically Create New Organizations in Control Hub disabled.

Common Cause:
  • The package type specified is syntactically valid (one of common_area_calling, webex_calling, webex_suite or webex_meetings), however that specific package type is not currently supported in this mode of operation.

Possible Solution:
  1. Perform the API request again with a supported package type.
400No
2006Insufficient Privileges
You do not have sufficient privileges to perform update/delete operations on this subscriber.

Common Cause:
  • The Partner Organization associated with the access token specified in the API request does not match the Partner Organization with which the subscriber was originally provisioned.

Possible Solution:
  1. Check to ensure the application making this API request has been authorized by a full administrator within the correct Partner Organization.
403No
2008Subscriber Provisioning Request Already Being Processed
A Subscriber Provision or Update API request for the same subscriber is already in being processed by Cisco Webex.

Common Cause:
  • Two Subscriber Provision or Update API requests have been sent concurrently for the same subscriber. Cisco Webex will reject any subsequent Provision/Update requests until it has responded to the initial request.

Possible Solution:
  1. Wait until you have received a response to the initial API request before performing another operation for the same subscriber.
400No
2011No Organization Administrator
The Subscriber Provision/Update operation could not be processed as the target customer organization on Cisco Webex does not have an administrator with Full Administrator role.

Common Cause:
  • All Wholesale Customer Organizations on Cisco Webex should have an administrator with Full Administrator role.
  • The administrator may be been deleted prior to this operation being performed.
Possible Solutions:
  1. Assign the Full Administrator role to an existing user in this organization before trying again.
  2. If there are no users in the organization, manually create a new user via Control Hub and apply the Full Administrator role.
409Yes
2016Customer and Partner Org Region Mismatch

Common Causes:

  • Partner is trying to on-board a pre-existing user or a new user using an email domain which is claimed by a Webex wholesale Organization in a different region.

Possible Solution:
  1. Ensure the user and partner are in the same region (for example: a user in the EU cannot be provisioned into US region or vice versa).
    409No
    2017Unable to provision Subscriber into an Existing Webex wholesale Organization
    The Subscriber Provision API request was rejected as an existing Webex wholesale Organization has been discovered either with subscriber’s exact matching email or domain of the the email, but automatic subscriber provisioning into this Webex wholeale Organization is forbidden.

    Common Cause:
    • This should only be encountered when provisioning the initial Subscriber in the wholesale customer.
      In that case, provisioning of the Subscriber into an existing Webex wholesale Organization is forbidden where there is no pre-existing relationship on Webex between the Partner and discovered Organization plus at least one of the following scenarios is true:
      1. The discovered Organization has more than 100 users.
      2. The Organization was discovered based on claimed domain only (i.e., the subscriber's email address was not found in the Organization, but the Organization has claimed the subscriber's email domain).

    Possible Solutions:
    1. Ensure that the email supplied for this subscriber is valid.
    409No
    2018Webex Organization already provisioned in a different cluster in the same region
    The Provision API request failed as the Webex Organization already has been provisioned with Webex wholesale services in a different cluster in the same region.

    Common Causes:
    • The Webex wholesale organization has been Provisioned in a different cluster in the same region.
    • The Webex wholesale organization had been previously provisioned under a different Partner Organization.
    409No
    2024Billing Reports not Found
    The Get / Delete Wholesale Billing Reports API request failed because the requested billing report is not found.

    Common Causes:
    • Trying to GET a billing report with a reportId that does not exist in the database.
    • Trying to DELETE a billing report with a reportId that does not exist in the database.
    Possible Solution:
    1. Use a valid billing reportId that is present in the database.
      To find out the list of reports for a specific partner (or/and) billing date, List Wholesale Billing Reports API can be used.
    404No
    2025Billing Reports generation is In Progress
    The request was rejected because the billing report generation is currently in progress.

    Common Cause:
    • Trying to create/delete a report when its generation is still IN_PROGRESS.
    Possible Solutions:
    1. Use the Get Wholesale Billing Reports API to obtain the status of the report before using Delete a Wholesale Billing Report API. Billing reports that are marked as COMPLETED/FAILED state can only be deleted. If the report that you intend to delete is IN_PROGRESS, wait and retry later.
    2. Use the Get Wholesale Billing Reports API to obtain the status of the report before using Create Wholesale Billing Report API. Use Create Wholesale Billing Report again only if the status was FAILED. Trying to create billing report operation for an already existing report would result in 2026 Billing Report Already Exists.
    409No
    2026Billing Report Already Exists
    Occurs when a partner tries to generate a report of a billingStartDate and billingEndDate for which the report was already generated.

    Possible Solutions:
    1. Make use of the Get Wholesale Billing Reports API to list reports and GET the concerned report.
    2. Use the Delete Wholesale Billing Report and Create Wholesale Billing Report APIs to recreate the billing report if required.
    409No
    2029Billing Reports Forbidden Access
    Insufficient privileges to access the Billing reports APIs.

    Common Cause:
    • The requesting user does not have the required privileges. The Billing Report APIs can be accessed by Partner Admins only.
    Possible Solution:
    1. The user making List/Get Wholesale Billing Report API request should be authorized by a Read - Only Administrator or Full Administrator or Sales Full Administrator within the correct Partner Organization.
    2. The user making Create/Delete Wholesale Billing Report API request should be authorized by a Full Administrator or Sales Full Administrator within the correct Partner Organization.
    403No
    2030Billing Reports Server Busy
    The request failed since the server is currently busy performing other billing report creation operations.

    Possible Solution:
    1. Retry the billing report creation at a later time.
    503No
    2501Invalid OrgId
    The organization specified in the request is not associated with any valid existing Webex organization.

    Common Causes
    • The customer orgId sent in the Wholesale customer provisioning request does not exist.
    • The customer org provided in the request is the self-signed up orgId.
    Possible Solutions:
    1. The Customer orgId provided in the request should be associated with pre-existing org.
    2. The orgId should not be self signed orgId.
    404No
    2502Wholesale customer is either in provisioning or updating or deleting status
    The requested operation cannot be processed because of a conflict in the current status of Customer provisioning.

    Common Causes
    • The wholesale org is either in provisioning or updating or deleting status.
    Possible Solutions:
    1. Provision the org once it moved to provisioned or error status .
    409No
    2503The wholesale customer already exist with different externalId
    The wholesale customer with the specified externalId is already associated with a different Webex organization.

    Common Causes:
    • The externalId is already associated with a different Webex organization.
    Possible Solutions:
    1. Provide the valid externalId.
    409No
    2504The wholesale customer is not fully provisioned
    User onboarding failed as the customer organization has not been successfully provisioned.

    Common Causes:
    • The wholesale Organization has not reached the provisioned status.
    Possible Solutions:
    1. Onboard the subscriber once the wholesale org has reached the provisioned status.
    409Yes
    2505The email is not matching with broadworksUserId
    The email provided in the request does not match the expected email for the specified broadworksUserId.

    Common Causes:
    • The email provided for the subscriber is not match with broadworksUserId.
    Possible Solutions:
    1. Please provide the broadwork user email in the request.
    409Yes
    2506The wholesale customer is not provisioned with requested package
    The customer organization does not have the requested package provisioned.

    Common Causes:
    • The wholesale customer is not provisioned with requested package.
    Possible Solutions:
    1. Provision the subscriber with the package which is already provisioned in the wholesale org.
    2. Update the wholesale org with required package and provision the subscriber.
    409Yes
    2507The subscriber already provisioned
    The specified user has already been previously onboarded.

    400Yes
    2508The broadworksUserId parameter is required
    The requested operation cannot be processed because the broadworksUserId parameter is required when provisioning the subscriber with the Webex For Broadworks Service.

    Common Causes:
    • The broadworksUserId parameter is not provided in the request.
    Possible Solutions:
    1. Please provide the valid broadworksUserId in the request.
    400Yes
    2509Invalid Billing Date provided for Wholesale Billing Reports Generation
    Invalid billingStartDate (or/and) billingEndDate request parameter provided in Wholesale Billing Reports API.

    Common Causes
    • billingStartDate request parameter is a later date than the billingEndDate request parameter.
    • billingStartDate and billingEndDate request parameter is a future date.
    Possible Solutions:
    1. The billingStartDate parameter must not be later date than the billingEndDate parameter and must be a past date.
    2. The billing Dates must not be a current date.
    3. The billing Dates must not be before 5 years from now.
    400No
    2510Invalid sortBy value in Wholesale Billing Reports
    Invalid value provided for the sortBy request parameter in Wholesale Billing Reports API.

    Possible Solution:
    1. The sortBy request parameter accepts only id,billingStartDate, billingEndDate or status as valid input.
    400No
    2511Invalid Wholesale Billing Report Status in Wholesale Billing Reports
    Invalid value provided for Report Status request parameter in Wholesale Billing Reports API.

    Possible Solution:
    1. The Report Status request parameter accepts only COMPLETED,IN-PROGRESS or FAILED as valid values.
    400No
    2512Invalid Wholesale Billing Report Type
    Invalid value provided for Wholesale Report Type request parameter in Wholesale Billing Reports API.

    Possible Solution:
    1. The Report Type request parameter accepts only PARTNER,CUSTOMER or USER as valid values.
    400No
    2513The wholesale customer has active workspace
    The wholesale customer with the specified customerId has active workspace in its Webex organization.

    Common Causes:
    • The wholesale customer has active workspace.

    Possible Solution:
    1. Delete all the active workspace from the wholesale customer and then perform the delete operation.
    409No
    2514The wholesale customer has active user
    The wholesale customer with the specified customerId has active users in its Webex organization.

    Common Causes:
    • The wholesale customer has active user.

    Possible Solution:
    1. Delete all the active user from the wholesale customer and then perform the delete operation.
    409No
    2515The partner organization does not have wholesale entitlements
    The Partner organization does not have the required entitlement for the specified provisioning package.

    Common Causes:
    • An attempt was made to provision a subscriber under the Partner organization which does not have the required entitlement for the particular package.

    Possible Solution:
    1. The Partner organization should be assigned the entitlement for the desired onboarding package.
    400No
    2516The partner organization does not have a wholesale subscription
    The Partner organization does not have the required subscription for the specified provisioning package.

    Common Causes:
    • An attempt was made to provision a subscriber under the Partner organization which does not have the required subscription for the particular package.

    Possible Solution:
    1. The Partner organization should be assigned the subscription for the desired onboarding package.
    400No
    2517Invalid Location ID
    The specified locationId parameter either does not exist or does not belong to the specified customer.

    Common Causes:
    • An attempt was made to provision a subscriber with a locationId parameter which does not exist or does not belong to the specified customer organization.

    Possible Solution:
    1. Provide a valid locationId parameter in the provisioning request
    400Yes
    2518Automatic selection of the location failed
    Automatic selection of the location for the customer organization can not be performed.

    Common Causes:
    • Customer attempt to provision the subscriber without providing the location details. Automatic selection of customer location can't be performed when customer doesn't not have any location or customer has multiple location.

    Possible Solution:
    1. The locationId parameter was not specified.
    2. Automatic selection of customer location could not be performed because the customer does not have any location.
    3. Automatic selection of customer location could not be performed because the customer has multiple locations.
    400Yes
    2519Subscription identifier for wholesale customers is missing
    The customer template does not have a configured subscription identifier.

    Common Causes:
    • An attempt was made to provision a subscriber under a Partner organization which does not have a subscription identifier configured in the customer template.

    Possible Solution:
    1. Configure the subscription identifier for the partner org in the customer template.
    400Yes
    2520A package is assigned to a user or workspace
    Unable to remove packages that are currently assigned to users and/or workspaces.

    Common Causes:
    • The package is assigned with active user or workspace.

    Possible Solution:
    1. Delete the associated user or workspace from the package and then perform the package delete operation.
    409No
    2521Invalid billing address for the customer
    The requested operation cannot be performed as the customer address provided in the request is invalid.

    Common Causes:
    • The request has invalid billing address of the customer.

    Possible Solution:
    1. Provide the valid billing address of the customer.
    400No
    2522Invalid phone number
    The phone number specified in the request is either invalid or does not belong to this customer.

    Common Causes:
    • The phone number provided in the request is not available.
    • Phone number provided in the request is does not belong to customer.

    Possible Solution:
    1. Provide the valid phone number for the subscriber.
    400Yes
    2523Invalid extension number
    The extension number specified in the request is either invalid or already in use.

    Common Causes:
    • The extension number provided in the request is not valid.

    Possible Solution:
    1. Provide the valid extension number for the subscriber.
    409Yes
    2524Invalid Cloud Connected PSTN provider ID
    The customer template does not have a Cloud Connected PSTN provider ID.

    Common Causes:
    • The Cloud Connected PSTN provider ID is null or empty in customer template.

    Possible Solution:
    1. Update the Cloud Connected PSTN provider ID in the template before provisioning.
    400No
    2525Webex Calling Resources Provisioning failed
    The requested operation failed to provision Webex Calling Resources.

    Common Causes:
    • Provisioning of the location might have failed
    • Provisioning parameters in the request might be invalid
    NANo
    2526Provisioning of numbers failed
    The requested operation failed to provision numbers for the Webex Calling Location.

    Common Causes:
    • The phone numbers are not available or invalid.
    NANo
    2527Provisioning of main number failed
    The requested operation failed to assign a main number to the Webex Calling Location.

    Common Causes:
    • The main number is not available or invalid.
    NANo
    2528Invalid Country Code
    Invalid country code provided in the calling attributes.

    Possible Solution:
    1. Please provide the valid ISO2 country code of the customer.
    400No
    2529Invalid State or Province Code of the country
    Invalid state or province provided in the calling attributes for the given country code.

    Possible Solution:
    1. Please provide the valid state or province code for the specified country.
    400No
    2530The state or province code is empty
    State or Province provided in the calling attributes cannot be empty for the given country code.

    Possible Solution:
    1. Please provide the valid state or province code for the specified country.
    400No
    2531The zip or postal code is empty
    Zip or Postal code provided in the calling attributes cannot be empty for the given country code.

    Possible Solution:
    1. Please provide the valid zip or postal code for the specified country.
    400No
    2532Invalid timezone
    Invalid timezone provided in the calling attributes for the given country code.

    Possible Solution:
    1. Please provide the valid timezone of the location.
    400No
    2533Invalid language
    Invalid language code provided in the calling attributes.

    Possible Solution:
    1. Please provide the valid language code of the location.
    400No
    2534Invalid Partner Wholesale Subscription ID
    The Partner Wholesale Subscription ID provided in the request is invalid.

    Possible Solution:
    1. Please provide the valid Partner Wholesale Subscription ID.
    400No
    2535BroadWorks ID cannot be updated
    The BroadWorks ID cannot be updated as there are existing users associated with the customer template.

    400No
    2539Country Code Not Permitted
    The customer country code is not supported for provisioning.

    400Yes
    5001Internal Server Error
    An unexpected error has occurred while processing the API request.

    Possible Solution:
    1. Please raise a Support Ticket if the issue persists.
    500Yes
    5003Invalid provisioningId
    The provisioningId provided in the request can not be found.

    Possible Solution:
    1. Provide the valid provisioningId in the request.
    404No
    anchorBackward Compatibility and Versioning
    anchor

    Our APIs change over time as we build new functionality. However, we are aware that API users need their applications to continue working as expected when the APIs change.

    For that reason, our APIs follow a backward-compatibility and versioning strategy as follows:

    When we add new API endpoints, new query parameters to existing endpoints, new optional fields in request bodies, and new data in response bodies, we do not necessarily create a new version of the API. Those kinds of changes should not affect the compatibility of the API with existing calls to the API, and we expect your applications to be robust to those kinds of improvements to the API.

    When we need to change the API outside of the scope described above, we create a new version of the API. For example, if we added a new required field to the request body, your application would not be aware of that requirement. If we changed the original version, your application would experience an unexpected failure.

    When we create a new version of an API, we continue to support the original version of the API for a reasonable period of time. This enables your application to continue working while you adapt it to using the new version of the API.

    We have an API framework team that works across the Cisco collaboration portfolio to approve any API changes before they are rolled out, ensuring that our backwards compatibility requirements are met and avoiding unpleasant surprises for our developer community.

    anchorAuthentication
    anchor

    When registering your application as an Integration, enable the following scopes to access all Webex for Wholesale APIs:

    Scope
    Usage
    spark-admin:wholesale_billing_reports_read
    Read or List Wholesale Billing Reports associated with a Partner, subscribed to Webex for Wholesale solution.
    spark-admin:wholesale_billing_reports_write
    Create or Delete Wholesale Billing Reports associated with a Partner, subscribed to Webex for Wholesale solution.

    If a Refresh Token expires, then the application can no longer generate the necessary access tokens for this API. A Service Provider admin needs to reauthorize the application to gain access to the APIs again. Therefore, it's important that your application maintain an active Refresh Token. Generating a new access token automatically renews the lifetime of your Refresh Token. An application that is regularly generating new access tokens will also be renewing it's Refresh Token lifetime. However, if the application becomes inactive for a long period of time (Refresh token expiry is 90 days) then it runs the risk of allowing the Refresh Token to expire. Therefore, it is recommended that your application run a scheduled task or job that generates a new access token using the Refresh Token. This ensures the Refresh Token will not expire, even during periods of inactivity.

    anchorAsynchronous Provisioning Model
    anchor

    Wholesale organization provisioning on Cisco Webex can take considerable time. Therefore, the Webex for Wholesale organization provisioning APIs don’t wait or block until organization is fully provisioned. Instead, the API responds quickly while initiating organization provisioning as a background task.

    You can design your application to query the wholesale organization later to determine its provisioning status. All representations of the organization through the APIs include a “status” attribute to indicate the organization’s provisioning status:

    On successful completion, the organization status changes to “provisioned”.If any error occurs during provisioning, the organization status transitions to “error”. The organization representation through these APIs also includes specific error codes and the reasons behind the provisioning error.

    anchorSubscriber Deletion
    anchor

    Webex for APIs supports both a soft and hard deletion model for subscribers. Soft Delete—The Webex for BroadWorks Delete a wholesale subscriber removes all entitlements and capabilities from when the subscriber was first provisioned for Webex for Wholesale. But, the subscriber remains provisioned within their Customer organization on Cisco Webex. The subscriber may continue to use Webex in line with their remaining capabilities. Hard Delete—If you wish to remove the subscriber completely from Cisco Webex, perform a DELETE with the People APIs.

    anchorOrganization Deletion
    anchor

    Follow the instructions below in order to delete an organization.

    • Delete all the subscribers from the organization using the Delete a wholesale subscriber API.
    • The removal of users may take some time depending on quantity of users.
    • Delete all the workspace from the organization.
    • The organization now can be deleted using Delete a wholesale customer API.
    anchorWebex Meetings Site Timezone
    anchor

    If a specific Webex Meetings site timezone is required, please specify the meeting timezone parameter in the organization provisioning request for the following packages:
    The wholesale organization provisioned for webex_suite package.
    The wholesale organization provisioned for webex_meetings package.

    If no timezone is specified in the provisioning request, the Webex Meetings site timezone for that package is set to a default based on the country assigned to the organization. In the case that a new organization is being created, the timezone is based on the country specified in the provisioning request.

    Here are the default cities/timezones for each country:

    CountryCity [Timezones]
    AfghanistanKabul [Asia/Kabul]
    AlbaniaAmsterdam [Europe/Amsterdam]
    AlgeriaWest Africa [Africa/Douala, Africa/Lagos]
    AndorraAmsterdam [Europe/Amsterdam]
    AngolaWest Africa [Africa/Douala, Africa/Lagos]
    AnguillaHalifax [America/Puerto_Rico, America/Halifax]
    Antigua and BarbudaHalifax [America/Puerto_Rico, America/Halifax]
    ArgentinaBuenos Aires [America/Argentina/La_Rioja, America/Argentina/Jujuy, America/Argentina/San_Luis, America/Argentina/Catamarca, America/Argentina/Santiago_del_Estero, America/Argentina/Ushuaia, America/Buenos_Aires, America/Argentina/Cordoba, America/Argentina/Salta, America/Argentina/San_Juan, America/Argentina/Tucuman, America/Argentina/Mendoza, America/Argentina/Rio_Gallegos, America/Argentina/Buenos_Aires]
    ArmeniaYerevan [Asia/Yerevan]
    ArubaHalifax [America/Puerto_Rico, America/Halifax]
    AustraliaSydney [Australia/Sydney]
    AustriaBerlin [Europe/Berlin, Europe/Warsaw, Europe/Vienna, America/Vaduz, Europe/Zurich]
    AzerbaijanBaku [Asia/Baku]
    BahamasIndiana [America/Indianapolis, America/Fort_Wayne]
    BahrainRiyadh [Asia/Riyadh]
    BangladeshMumbai [Asia/Kolkata]
    BarbadosHalifax [America/Puerto_Rico, America/Halifax]
    BelarusMoscow [Europe/Moscow]
    BelgiumBrussels [Europe/Brussels]
    BelizeChicago [America/Chicago, America/Costa_Rica]
    BeninWest Africa [Africa/Douala, Africa/Lagos]
    BermudaHalifax [America/Puerto_Rico, America/Halifax]
    BhutanAlmaty [Asia/Almaty]
    BoliviaLa Paz [America/La_Paz]
    Bonaire, Saint Eustatius and SabaHalifax [America/Puerto_Rico, America/Halifax]
    Bosnia and HerzegovinaAmsterdam [Europe/Amsterdam]
    BotswanaWindhoek [Africa/Windhoek]
    BrazilBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    Brunei DarussalamKuala Lumpur [Asia/Kuala_Lumpur]
    BulgariaHelsinki [Europe/Helsinki]
    BurundiWindhoek [Africa/Windhoek]
    CambodiaBangkok [Asia/Bangkok, Asia/Saigon]
    CameroonWest Africa [Africa/Douala, Africa/Lagos]
    CanadaToronto [America/Montreal, America/Toronto]
    Cape VerdeCape Verde [Atlantic/Cape_Verde]
    Cayman IslandsPanama [America/Panama]
    ChileSantiago [America/Santiago, America/Punta_Arenas, Pacific/Easter]
    ChinaBeijing [Asia/Hong_Kong, Asia/Shanghai]
    ColombiaBogota [America/Guayaquil, America/Bogota, America/Lima, America/Galapagos]
    ComorosNairobi [Africa/Nairobi]
    Costa RicaChicago [America/Chicago, America/Costa_Rica]
    Cote d'IvoireLondon [Europe/London, Europe/Dublin]
    CroatiaParis [Europe/Paris, Europe/Luxembourg, America/Monaco, Europe/Copenhagen]
    CuracaoCaracas [America/Caracas]
    CyprusBucharest / Chisinau [Europe/Tallinn, Asia/Nicosia, Europe/Bucharest, Europe/Riga, Europe/Kiev, Europe/Vilnius]
    Czech RepublicPrague [Europe/Ljubljana, Europe/Budapest, Europe/Zagreb, Europe/Prague]
    DenmarkParis [Europe/Paris, Europe/Luxembourg, America/Monaco, Europe/Copenhagen]
    Dominican RepublicCaracas [America/Caracas]
    EcuadorBogota [America/Guayaquil, America/Bogota, America/Lima, America/Galapagos]
    EgyptCairo [Africa/Cairo]
    El SalvadorChicago [America/Chicago, America/Costa_Rica]
    EstoniaBucharest / Chisinau [Europe/Tallinn, Asia/Nicosia, Europe/Bucharest, Europe/Riga, Europe/Kiev, Europe/Vilnius]
    EthiopiaNairobi [Africa/Nairobi]
    Faroe IslandsLondon [Europe/London, Europe/Dublin]
    FijiFiji [Pacific/Fiji]
    FinlandHelsinki [Europe/Helsinki]
    FranceParis [Europe/Paris, Europe/Luxembourg, America/Monaco, Europe/Copenhagen]
    French GuianaBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    French PolynesiaHonolulu [Pacific/Honolulu]
    GeorgiaIstanbul [Europe/Istanbul]
    GermanyBerlin [Europe/Berlin, Europe/Warsaw, Europe/Vienna, America/Vaduz, Europe/Zurich]
    GhanaLondon [Europe/London, Europe/Dublin]
    GreeceAthens [Europe/Athens]
    GreenlandNuuk [America/Godthab]
    GuadeloupeCaracas [America/Caracas]
    GuatemalaMexico City [America/Mexico_City]
    HondurasTegucigalpa [America/Tegucigalpa]
    Hong KongBeijing [Asia/Hong_Kong, Asia/Shanghai]
    HungaryPrague [Europe/Ljubljana, Europe/Budapest, Europe/Zagreb, Europe/Prague]
    IcelandReykjavik [Atlantic/Reykjavik]
    IndiaColombo [Asia/Colombo]
    IndonesiaJakarta [Asia/Jakarta]
    IraqRiyadh [Asia/Riyadh]
    IrelandLondon [Europe/London, Europe/Dublin]
    Isle of ManLondon [Europe/London, Europe/Dublin]
    IsraelTel Aviv [Asia/Tel_Aviv, Asia/Jerusalem]
    ItalyRome [America/Tunis, Europe/Malta, Europe/Rome]
    JamaicaBogota [America/Guayaquil, America/Bogota, America/Lima, America/Galapagos]
    JapanTokyo [Asia/Tokyo]
    JerseyLondon [Europe/London, Europe/Dublin]
    JordanAmman [Asia/Amman]
    KazakhstanAlmaty [Asia/Almaty]
    KenyaNairobi [Africa/Nairobi]
    Korea, Republic ofSeoul [Asia/Seoul]
    KuwaitRiyadh [Asia/Riyadh]
    KyrgyzstanAlmaty [Asia/Almaty]
    Lao People's Democratic RepublicBangkok [Asia/Bangkok, Asia/Saigon]
    LatviaBucharest / Chisinau [Europe/Tallinn, Asia/Nicosia, Europe/Bucharest, Europe/Riga, Europe/Kiev, Europe/Vilnius]
    LebanonWindhoek [Africa/Windhoek]
    Libyan Arab JamahiriyaWindhoek [Africa/Windhoek]
    LiechtensteinBerlin [Europe/Berlin, Europe/Warsaw, Europe/Vienna, America/Vaduz, Europe/Zurich]
    LithuaniaBucharest / Chisinau [Europe/Tallinn, Asia/Nicosia, Europe/Bucharest, Europe/Riga, Europe/Kiev, Europe/Vilnius]
    LuxembourgParis [Europe/Paris, Europe/Luxembourg, America/Monaco, Europe/Copenhagen]
    MacaoBeijing [Asia/Hong_Kong, Asia/Shanghai]
    MacedoniaBerlin [Europe/Berlin, Europe/Warsaw, Europe/Vienna, America/Vaduz, Europe/Zurich]
    MadagascarNairobi [Africa/Nairobi]
    MalawiWindhoek [Africa/Windhoek]
    MalaysiaKuala Lumpur [Asia/Kuala_Lumpur]
    MaldivesYekaterinburg [Asia/Yekaterinburg]
    MaliLondon [Europe/London, Europe/Dublin]
    MaltaRome [America/Tunis, Europe/Malta, Europe/Rome]
    Marshall IslandsMarshall Islands [Pacific/Majuro]
    MartiniqueBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    MauritiusAbu Dhabi, Muscat [Asia/Dubai]
    MayotteNairobi [Africa/Nairobi]
    MexicoMexico City [America/Mexico_City]
    Moldova, Republic ofParis [Europe/Paris, Europe/Luxembourg, America/Monaco, Europe/Copenhagen]
    MonacoParis [Europe/Paris, Europe/Luxembourg, America/Monaco, Europe/Copenhagen]
    MongoliaBeijing [Asia/Hong_Kong, Asia/Shanghai]
    MontenegroBerlin [Europe/Berlin, Europe/Warsaw, Europe/Vienna, America/Vaduz, Europe/Zurich]
    MoroccoCasablanca [Africa/Casablanca]
    MozambiqueWindhoek [Africa/Windhoek]
    NamibiaWindhoek [Africa/Windhoek]
    NepalKathmandu [Asia/Kathmandu]
    NetherlandsAmsterdam [Europe/Amsterdam]
    New CaledoniaSolomon Is [Pacific/Guadalcanal]
    New ZealandWellington [Pacific/Auckland]
    NicaraguaTegucigalpa [America/Tegucigalpa]
    NigeriaWest Africa [Africa/Douala, Africa/Lagos]
    NorwayOslo [Europe/Oslo]
    OmanAbu Dhabi, Muscat [Asia/Dubai]
    PakistanIslamabad [Asia/Karachi]
    Palestinian TerritoryTel Aviv [Asia/Tel_Aviv, Asia/Jerusalem]
    PanamaPanama [America/Panama]
    Papua New GuineaGuam [Pacific/Guam]
    ParaguayAsuncion [America/Asuncion]
    PeruBogota [America/Guayaquil, America/Bogota, America/Lima, America/Galapagos]
    PhilippinesBeijing [Asia/Hong_Kong, Asia/Shanghai]
    PolandBerlin [Europe/Berlin, Europe/Warsaw, Europe/Vienna, America/Vaduz, Europe/Zurich]
    PortugalLondon [Europe/London, Europe/Dublin]
    Puerto RicoHalifax [America/Puerto_Rico, America/Halifax]
    QatarRiyadh [Asia/Riyadh]
    ReunionAbu Dhabi, Muscat [Asia/Dubai]
    RomaniaBucharest / Chisinau [Europe/Tallinn, Asia/Nicosia, Europe/Bucharest, Europe/Riga, Europe/Kiev, Europe/Vilnius]
    Russian FederationMoscow [Europe/Moscow]
    RwandaWindhoek [Africa/Windhoek]
    Saint Kitts and NevisBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    Saint LuciaBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    Saint MartinBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    Saint Vincent and the GrenadinesBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    San MarinoRome [America/Tunis, Europe/Malta, Europe/Rome]
    Saudi ArabiaRiyadh [Asia/Riyadh]
    SenegalLondon [Europe/London, Europe/Dublin]
    SerbiaParis [Europe/Paris, Europe/Luxembourg, America/Monaco, Europe/Copenhagen]
    SeychellesAbu Dhabi, Muscat [Asia/Dubai]
    SingaporeSingapore [Asia/Singapore]
    Sint MaartenCaracas [America/Caracas]
    SlovakiaPrague [Europe/Ljubljana, Europe/Budapest, Europe/Zagreb, Europe/Prague]
    SloveniaParis [Europe/Paris, Europe/Luxembourg, America/Monaco, Europe/Copenhagen]
    South AfricaPretoria [Africa/Johannesburg]
    SpainMadrid [Europe/Gibraltar, Europe/Madrid]
    Sri LankaColombo [Asia/Colombo]
    SurinameBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    SwedenStockholm [Europe/Stockholm]
    SwitzerlandBerlin [Europe/Berlin, Europe/Warsaw, Europe/Vienna, America/Vaduz, Europe/Zurich]
    TaiwanTaipei [Asia/Taipei]
    TajikistanYekaterinburg [Asia/Yekaterinburg]
    Tanzania, United Republic ofNairobi [Africa/Nairobi]
    ThailandBangkok [Asia/Bangkok, Asia/Saigon]
    Timor-LesteSeoul [Asia/Seoul]
    TogoLondon [Europe/London, Europe/Dublin]
    TongaTonga [Pacific/Tongatapu]
    Trinidad and TobagoBrasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    TunisiaWest Africa [Africa/Douala, Africa/Lagos]
    TurkeyIstanbul [Europe/Istanbul]
    TurkmenistanYekaterinburg [Asia/Yekaterinburg]
    Turks and Caicos IslandsBogota [America/Guayaquil, America/Bogota, America/Lima, America/Galapagos]
    UgandaNairobi [Africa/Nairobi]
    UkraineBucharest / Chisinau [Europe/Tallinn, Asia/Nicosia, Europe/Bucharest, Europe/Riga, Europe/Kiev, Europe/Vilnius]
    United Arab EmiratesAbu Dhabi, Muscat [Asia/Dubai]
    United KingdomLondon [Europe/London, Europe/Dublin]
    United StatesSan Francisco [America/Los_Angeles]
    United States Minor Outlying IslandsHonolulu [Pacific/Honolulu]
    UruguayMontevideo [America/Montevideo]
    UzbekistanYekaterinburg [Asia/Yekaterinburg]
    VenezuelaCaracas [America/Caracas]
    VietnamBangkok [Asia/Bangkok, Asia/Saigon]
    Virgin Islands, U.S.Brasilia [America/Cuiaba, America/Sao_Paulo, America/Porto_Velho, America/Eirunepe, America/Campo_Grande, America/Belem, America/Recife, America/Bahia, America/Noronha, America/Araguaina, America/Boa_Vista, America/Manaus, America/Santarem, America/Fortaleza, America/Maceio, America/Rio_Branco]
    ZambiaCairo [Africa/Cairo]
    ZimbabweCairo [Africa/Cairo]

    In the event of a problem with converting the country to a Webex Meetings Site Timezone, the following default per cluster value will be used:

    ClusterCity [Timezones for this city]
    US-A (ACHM)New York [America/New_York]
    US-B (AORE)San Francisco [America/Los_Angeles]
    EU (AFRA)London [Europe/London, Europe/Dublin]