Source note · Webex Calling bulk provisioning in Control Hub
Starting a second move-number job while one is already running appears to be rejected with HTTP 409.
inferred · Checked 2026-09-25
If another move number job request is initiated while a move job is in progress, the API call will receive a 409 HTTP status code
- Vendor
- Cisco
- Product
- Webex Calling APIs
- Subsystem
- Manage Numbers jobs API
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Status
- inferred
- Checked
- 2026-09-25
Sources
- wxc_sdk.telephony.jobs module documentation — wxc_sdk project (Read the Docs) · tier 4 archived vendor documentation · wxc_sdk.telephony.jobs > ManageNumbersJobsApi docstring
Cite this note
APA
WarmTransfer. (2026, September 25). Webex Calling bulk provisioning in Control Hub: source note webex-calling-bulk-provisioning-api-number-job-409. WarmTransfer. https://warmtransfer.net/knowledge/claims/webex-calling-bulk-provisioning-api-number-job-409
BibTeX
@misc{warmtransfer-claim-webex-calling-bulk-provisioning-api-number-job-409,
title = {Webex Calling bulk provisioning in Control Hub: source note webex-calling-bulk-provisioning-api-number-job-409},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/webex-calling-bulk-provisioning-api-number-job-409},
note = {Source note webex-calling-bulk-provisioning-api-number-job-409, checked 2026-09-25}
}