# The Webex Contact Center developer sandbox

Canonical: https://warmtransfer.net/knowledge/webex-cc-developer-sandbox

Last verified: 2026-09-22

A Contact Center Developer Sandbox gives a requester administrator access to a licensed Webex Contact Center sandbox for creating and testing platform capabilities that are not available with Webex free plans[^41]. A licensed organisation is required because Webex free plans cannot access those platform features[^28].

## Provisioning and Account Setup

Using a Contact Center Developer Sandbox requires first signing in to the Webex Contact Center Developer Portal, and a new free Webex account can be created for this purpose[^46]. A Webex developer sandbox is requested by selecting Request a Sandbox on the developer portal, accepting the terms dialog, and supplying an email address if prompted, after which credentials arrive by email[^43]. If a request fails, Cisco advises signing out of the existing Webex account and resubmitting the request with an email address[^45]. Webex partners and existing customers can develop against their own organisations directly and do not need a developer sandbox for embedded-app development, though it remains available for isolated testing[^36].

Sandbox credentials arrive in an email titled Collab Toolbox Provisioning Notification[^19]. The provisioning email contains the Webex site name, DNS domain, administrator username, administrator password, and Webex site URL[^40]. A sandbox organisation is issued a DNS domain under wbx.ai and a Webex site URL under webex.com, both derived from a generated organisation name[^18]. Standard Webex developer sandboxes are provisioned on the legacy meetings platform; a sandbox on the Webex Suite Meeting Platform requires contacting support for special configuration[^27].

No changes in Webex Control Hub are required to use the developer sandbox, although the administrator account can sign in to Control Hub to customise Contact Center settings and view metrics[^15]. Cisco instructs administrators to sign in to Webex Control Hub at https://admin.webex.com from a fresh private or incognito browser window using the credentials from the provisioning email[^26]. Cisco recommends the latest desktop version of Google Chrome or Mozilla Firefox for Webex Contact Center portals, stating that other browsers may produce unexpected results[^7]. Portals are not designed for mobile devices[^34]. Problems with a developer sandbox are raised through the developer portal Support page[^47].

## Default Configuration and Voice Routing

Webex Calling is the default calling platform provisioned in a Webex Contact Center developer sandbox[^8].

| Resource | Default Provisioning | Notes |
| --- | --- | --- |
| Administrators | 1 administrator user[^37] | Authorised to access Webex Control Hub[^15] |
| Contact Center Users | 2 default users[^56] | Premium agent (extension 1001) and supervisor (extension 1002)[^21] |
| PSTN Numbers | 2 numbers[^57] | Main number assigned to default Webex Calling location (reserved) and entry point number assigned to default inbound entry point[^57][^30] |
| Desktop Profiles | 2 profiles[^17] | 1 with auto-wrap-up enabled (ends calls with a default wrap-up code) and 1 without[^17][^4] |
| User Profiles | 5 pre-configured profiles[^58] | Administrator Only Profile, Administrator Profile, Premium Agent User Profile, Standard Agent User Profile, Supervisor Profile[^58] |
| Teams | 1 agent-based team[^52] | Default team[^52] |
| Routing Queue | 1 inbound voice queue[^42] | Preconfigured inbound voice queue[^42] |
| Multimedia Profiles | 1 default profile[^31] | Default multimedia profile[^31] |
| Audio Files | Default hold music and greeting message[^2] | Stored audio files[^2] |

In a sandbox, the main PSTN number supplied in the provisioning email is dialled to reach an agent signed in to Agent Desktop[^29]. The sources differ on the main number's role: reserved to the default Webex Calling location on the sandbox page, and dialled to reach a signed-in agent on the getting-started page[^30][^29]. The default flow plays default hold music and redirects the call to the default inbound queue[^24]. Business hours mapped to the default inbound entry point and basic flow remain active for 60 days from the time the sandbox is created[^5].

## Validity and Environment Limits

All Webex Contact Center developer sandboxes have a validity period of 180 days[^59]. Extending sandbox validity is done by contacting Webex Developer Support; the documentation names no self-service extension mechanism[^20]. WarmTransfer's reading of the sources is that because the 60-day default business-hours window expires before the sandbox itself, a sandbox can remain valid while its default entry point stops routing on the original schedule[^6].

Each Webex Developer Sandbox is limited to a maximum of 10 account users, for validation and test purposes only[^53]. Cisco may audit sandbox accounts and reserves the right to remove users in excess of 10 account users or terminate the sandbox environment for developer resource misuse[^3].

## API Authentication and Service Apps

Webex Contact Center API requests carry an access token in an Authorization HTTP header across 3 supported token types: personal access tokens, bot tokens, and OAuth tokens issued to an Integration[^55]. Personal access tokens expire 12 hours after the developer signs in to the portal[^38]. Cisco states that personal access tokens should not be used in production environments and that an Integration should be created to obtain OAuth tokens from authenticating users instead[^39]. Cisco instructs developers to read the expiration values returned by the service rather than assuming a fixed token lifetime[^54].

Authorising an integration for Webex Contact Center administrator APIs requires a Webex account backed by Cisco Webex Common Identity and the appropriate administrator role in Control Hub[^1]. Cisco directs developers working in a free Webex organisation to request a sandbox to obtain the administrator account required to test service apps[^51]. Only a Full Admin can authorise a Webex Contact Center service app; read-only administrators and device administrators are insufficient[^48]. A newly created service app is private and can only be authorised by its creator within their own organisation; authorisation outside that organisation requires manual review through Webex AppHub submission[^50]. WarmTransfer's reading of the sources is that a service app validated inside a developer sandbox cannot simply be pointed at a customer tenant, because authorisation outside the creating organisation requires a separate AppHub review and a Full Admin of that customer tenant[^49].

Flow Designer documents Export a flow and Import a flow operations, which provide the documented mechanism to carry a flow built in one organisation into another[^25].

## Webex Connect Sandbox

A Webex Connect sandbox pre-provisions phone numbers and sender IDs for prototyping across SMS, voice, and WhatsApp only[^10]. Webex Connect sandbox registration requires a business email address and does not accept free domains such as Gmail.[^9]. A Webex Connect sandbox account may register up to 5 test numbers: 1 primary number that cannot be changed and 4 secondary numbers[^12]. Webex Connect documents an upgrade path from sandbox to full platform mode that unlocks further channels including email, push, RCS, Facebook Messenger, and Apple Messages for Business, plus template management, Bot Builder, analytics, SSO, audit trail, and higher API throughput[^14].

## See also

- See also [Webex Contact Center Agent Desktop and widgets](https://warmtransfer.net/knowledge/webex-cc-agent-desktop).
- See also [Webex Contact Center APIs and webhooks](https://warmtransfer.net/knowledge/webex-cc-apis).
- See also [Webex Contact Center business hours overrides and holiday lists](https://warmtransfer.net/knowledge/webex-cc-business-hours-holidays).
- See also [Webex Contact Center Flow Designer architecture](https://warmtransfer.net/knowledge/webex-cc-flow-designer).
- See also [Webex Contact Center queues teams and routing strategies](https://warmtransfer.net/knowledge/webex-cc-routing).
- See also [Webex Contact Center voice channel and PSTN options](https://warmtransfer.net/knowledge/webex-cc-voice-channels).
- See also [Webex Connect digital channel flow orchestration](https://warmtransfer.net/knowledge/webex-connect-digital-flows).

## Applicability

The Suite Sandbox offered on the Webex for Government FedRAMP developer portal supports commercial APIs rather than FedRAMP-only APIs[^23].

## What remains uncertain

Whether a sandbox administrator can enable digital channels outbound campaigns WFO or AI features in a Contact Center sandbox after provisioning is not covered by the sources below. The current documented procedure for requesting a Contact Center developer sandbox including any rule that existing Webex sandboxes must be deleted first and any stated wait times is not covered by the sources below. What happens to the sandbox organisation and its data when the 180-day validity lapses is not covered by the sources below. Whether the 10 account user cap from the generic Webex sandbox guide applies to a Contact Center sandbox and whether it counts Contact Center agent licences is not covered by the sources below. Whether Flow Designer export and import works across organisations and what a flow loses when moved between tenants is not covered by the sources below. Whether Webex Contact Center API rate limits differ between a developer sandbox and a production tenant is not covered by the sources below. Which region or data centre a Contact Center developer sandbox is provisioned in and whether the requester can choose is not covered by the sources below. The Webex Connect sandbox as its own corpus topic covering quotas channel scope and the upgrade path to full platform mode is not covered by the sources below.

## Sources

[^1]: To authorise an integration for Webex Contact Center administrator APIs the user must hold a Webex account backed by Cisco Webex Common Identity and the appropriate administrator role in Control Hub. Source: [Webex Contact Center - Authentication](https://developer.webex.com/webex-contact-center/docs/authentication), Authentication > organisational requirements for Contact Center administrator APIs. Checked 2026-09-22.
[^2]: A Webex Contact Center developer sandbox is provisioned with default hold music and a default greeting message as audio files. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 9 (Audio files). Checked 2026-09-22.
[^3]: Cisco may audit Webex Developer Sandbox accounts and reserves the right to remove users in excess of 10 account users or to terminate the sandbox environment for developer resource misuse. Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Webex Developer Sandbox Guide > Do I need a Developer Sandbox?, limitation note, second sentence. Checked 2026-09-22.
[^4]: The auto-wrap-up desktop profile in a Webex Contact Center developer sandbox ends the call with a default wrap-up code instead of requiring the agent to choose one. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 3, parenthetical. Checked 2026-09-22.
[^5]: The business hours mapped to the default inbound entry point and default basic flow of a Webex Contact Center developer sandbox are active for 60 days from the time the sandbox is created. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 11 (Business Hours). Checked 2026-09-22.
[^6]: The 60-day default business-hours window of a Webex Contact Center developer sandbox expires before the sandbox itself, so a sandbox can remain valid while its default entry point stops routing on the original schedule (inferred). Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 11, read against the 180-day NOTE in the Introduction. Checked 2026-09-22.
[^7]: Cisco recommends the latest desktop version of Google Chrome or Mozilla Firefox for the Webex Contact Center portals and states other browsers may produce unexpected results. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Introduction, Caution block. Checked 2026-09-22.
[^8]: Webex Calling is the default calling platform provisioned in a Webex Contact Center developer sandbox. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 1 (Webex calling for Voice). Checked 2026-09-22.
[^9]: Webex Connect sandbox registration requires a business email address and does not accept free domains such as Gmail, and permits at most three one-time-password attempts during registration. Source: [Getting Started with Sandbox](https://help.webexconnect.io/docs/getting-started-with-sandbox), Getting Started with Sandbox > registration limits. Checked 2026-09-22.
[^10]: The Webex Connect sandbox pre-provisions phone numbers and sender IDs for prototyping across SMS, voice and WhatsApp only. Source: [Getting Started with Sandbox](https://help.webexconnect.io/docs/getting-started-with-sandbox), Getting Started with Sandbox > what the sandbox provides. Checked 2026-09-22.
[^11]: The Webex Connect sandbox is a separate offer from the Webex Contact Center developer sandbox, with its own channel scope, quotas and registration rules (inferred). Source: [Getting Started with Sandbox](https://help.webexconnect.io/docs/getting-started-with-sandbox), Getting Started with Sandbox, whole page, contrasted with the Contact Center Sandbox page on developer.webex.com. Checked 2026-09-22.
[^12]: A Webex Connect sandbox account may register up to five test numbers: one primary number that cannot be changed and four secondary numbers that must share the primary number's country. Source: [Sandbox FAQs](https://help.webexconnect.io/docs/sandbox-faqs), Sandbox FAQs > test number registration question. Checked 2026-09-22.
[^13]: A Webex Connect sandbox account allows 10,000 combined SMS and WhatsApp API requests within 365 days of account creation, after which requests fail with error code 7020. Source: [Sandbox FAQs](https://help.webexconnect.io/docs/sandbox-faqs), Sandbox FAQs > transaction limit question. Checked 2026-09-22.
[^14]: Webex Connect documents an upgrade path from sandbox to full platform mode that unlocks further channels including email, push, RCS, Facebook Messenger and Apple Messages for Business, plus template management, Bot Builder, analytics, SSO, audit trail and higher API throughput. Source: [Sandbox FAQs](https://help.webexconnect.io/docs/sandbox-faqs), Sandbox FAQs > upgrading to full platform mode. Checked 2026-09-22.
[^15]: No change in Webex Control Hub is required to use a Webex Contact Center developer sandbox, although the administrator account can sign in to Control Hub to customise Contact Center settings and view metrics. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Webex Control Hub Access, first paragraph. Checked 2026-09-22.
[^16]: Practitioners have pointed colleagues to Cisco dCloud and to the legacy developer.webex-cx.com sandbox page as routes to a Webex Contact Center test environment (field report). Source: [Solved: Request for Webex Contact Center Sandbox](https://community.cisco.com/t5/contact-center/request-for-webex-contact-center-sandbox/td-p/4740662), reply by bill.king1 (VIP), 04-18-2023. Checked 2026-09-22.
[^17]: A Webex Contact Center developer sandbox is provisioned with two desktop profiles, one with auto-wrap-up enabled and one without. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 3 (Desktop Profiles). Checked 2026-09-22.
[^18]: A Webex Contact Center developer sandbox organisation is issued a DNS domain under wbx.ai and a Webex site URL under webex.com, both derived from a generated organisation name. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Provisioning Email > DNS Domain and Webex Site URL fields. Checked 2026-09-22.
[^19]: The Webex developer sandbox credentials arrive in an email titled Collab Toolbox Provisioning Notification. Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Webex Developer Sandbox Guide > Sandbox Quick Start, step 3. Checked 2026-09-22.
[^20]: Extending the validity of a Webex Contact Center developer sandbox is done by contacting Webex Developer Support; the documentation names no self-service extension mechanism. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Introduction, boldfaced NOTE, second sentence. Checked 2026-09-22.
[^21]: The two Contact Center user accounts in a Webex Contact Center developer sandbox are issued extensions 1001 for the premium agent and 1002 for the supervisor agent. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Provisioning Email > Two Contact Center users. Checked 2026-09-22.
[^22]: The Webex developer portal Support FAQ states nothing about sandbox validity periods, expiry, extension, user limits, deletion, or migrating data from a sandbox to a production environment. Source: [Support - Frequently Asked Questions](https://developer.webex.com/explore/docs/frequently-asked-questions), Support FAQ, whole page as retrieved 2026-09-22. Checked 2026-09-22.
[^23]: The Suite Sandbox offered on the Webex for Government FedRAMP developer portal supports commercial APIs rather than FedRAMP-only APIs. Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Build - Developer Sandbox > Suite Sandbox. Checked 2026-09-22.
[^24]: The default flow in a Webex Contact Center developer sandbox plays the default hold music and redirects the call to the default inbound queue. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 10 (Flow). Checked 2026-09-22.
[^25]: Webex Contact Center Flow Designer documents Export a flow and Import a flow operations, which is the documented mechanism by which a flow built in one organisation can be carried into another. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Build and manage flows with Flow Designer > table of contents, entries 'Export a flow' and 'Import a flow'. Checked 2026-09-22.
[^26]: Cisco instructs sandbox administrators to sign in to Webex Control Hub at https://admin.webex.com from a fresh private or incognito browser window using the credentials from the provisioning email. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Webex Control Hub Access, numbered steps 1 to 4. Checked 2026-09-22.
[^27]: Standard Webex developer sandboxes are provisioned on the legacy meetings platform, and a sandbox on the Webex Suite Meeting Platform requires contacting support for special configuration. Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Webex Developer Sandbox Guide > Sandbox Quick Start, note about the Webex Suite Meeting Platform. Checked 2026-09-22.
[^28]: A Webex developer sandbox exists because a licensed organisation is required to test Webex platform features that are not available to Webex free plans. Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Webex Developer Sandbox Guide > Do I need a Developer Sandbox?. Checked 2026-09-22.
[^29]: In a Webex Contact Center developer sandbox the main PSTN number, supplied in the provisioning email, is the number dialled to reach an agent signed in to Agent Desktop. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 1. Checked 2026-09-22.
[^30]: The main PSTN number of a Webex Contact Center developer sandbox is assigned to the default Webex Calling location and is described as reserved. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Provisioning Email > Two PSTN Numbers, first bullet. Checked 2026-09-22.
[^31]: A Webex Contact Center developer sandbox is provisioned with one default multimedia profile. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 6 (Multimedia profile). Checked 2026-09-22.
[^32]: Cisco documents no procedure for converting a Webex Contact Center developer sandbox into a production tenant, and no procedure for transferring its licences, PSTN numbers or organisation identity to one (inferred). Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox, whole page, read against the Webex Developer Sandbox Guide and the developer portal Support FAQ. Checked 2026-09-22.
[^33]: The Webex for Government developer sandbox guide carries no Webex Contact Center specific sandbox content, so no FedRAMP Contact Center sandbox offer is documented there (inferred). Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Build - Developer Sandbox, whole page. Checked 2026-09-22.
[^34]: The Webex Contact Center portals are not designed for mobile devices. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Introduction, Caution block, final sentence. Checked 2026-09-22.
[^35]: As retrieved on 2026-09-22 the Contact Center Sandbox page documents what a sandbox contains and how to sign in to it but contains no step-by-step procedure for requesting one. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox, whole page: headings Introduction, Sandbox Vidcasts, Sandbox Contents, Sandbox Provisioning Email, Webex Control Hub Access, Sandbox Support. Checked 2026-09-22.
[^36]: Webex partners and existing Webex customers can develop against their own organisation and do not need a developer sandbox, which remains available for optional isolated testing. Source: [Support - Frequently Asked Questions](https://developer.webex.com/explore/docs/frequently-asked-questions), Support FAQ > question on whether a developer sandbox is required. Checked 2026-09-22.
[^37]: A Webex Contact Center developer sandbox is provisioned with exactly one administrator user. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 2 (Administrator). Checked 2026-09-22.
[^38]: Personal access tokens on the Webex Contact Center developer portal expire 12 hours after the developer signs in to the portal. Source: [Webex Contact Center - Getting Started](https://developer.webex.com/webex-contact-center/docs/getting-started), Getting Started > Personal access tokens. Checked 2026-09-22.
[^39]: Cisco states that personal access tokens should not be used in production environments and that an Integration should be created to obtain OAuth tokens from authenticating users instead. Source: [Webex Contact Center - Getting Started](https://developer.webex.com/webex-contact-center/docs/getting-started), Getting Started > Personal access tokens. Checked 2026-09-22.
[^40]: After a Webex Contact Center developer sandbox is created the requester receives a provisioning email containing the Webex site name, DNS domain, administrator username, administrator password and Webex site URL. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Provisioning Email > Webex Site and Administrator Credentials. Checked 2026-09-22.
[^41]: A Contact Center Developer Sandbox gives the requester administrator access to a licensed Webex Contact Center sandbox for creating and testing platform capabilities that are not available with Webex free plans. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Introduction, first paragraph. Checked 2026-09-22.
[^42]: A Webex Contact Center developer sandbox is provisioned with one preconfigured inbound voice queue. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 8 (Queue). Checked 2026-09-22.
[^43]: A Webex developer sandbox is requested by selecting Request a Sandbox on the developer portal, accepting the terms dialog and supplying an email address if prompted; credentials then arrive by email. Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Webex Developer Sandbox Guide > Sandbox Quick Start, To request a Sandbox Organization, steps 1 to 3. Checked 2026-09-22.
[^44]: Before a self-service Contact Center sandbox existed, developers requested one by posting on the Cisco Community, and a Cisco employee gave a tentative availability of February or March 2023 for a Contact Center developer sandbox (field report). Source: [Solved: Request for Webex Contact Center Sandbox](https://community.cisco.com/t5/contact-center/request-for-webex-contact-center-sandbox/td-p/4740662), opening post 12-16-2022 and reply by Arunabh Bhattacharjee (Cisco Employee), 01-04-2023. Checked 2026-09-22.
[^45]: If a Webex developer sandbox request fails, Cisco advises signing out of the existing Webex account and resubmitting the request with an email address. Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Webex Developer Sandbox Guide > Sandbox Quick Start, note following step 2. Checked 2026-09-22.
[^46]: Using a Contact Center Developer Sandbox requires first being signed in to the Webex Contact Center Developer Portal, and a new free Webex account can be created for that purpose. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Introduction, second paragraph. Checked 2026-09-22.
[^47]: Problems with a Webex Contact Center developer sandbox are raised through the developer portal Support page. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Support. Checked 2026-09-22.
[^48]: Only a Full Admin can authorise a Webex Contact Center service app; read-only administrators and device administrators are insufficient. Source: [Contact Center Service Apps](https://developer.webex.com/admin/docs/contact-center-service-apps), Contact Center Service Apps > authorization requirements. Checked 2026-09-22.
[^49]: A service app validated inside a Webex Contact Center developer sandbox cannot simply be pointed at a customer tenant, because authorisation outside the creating organisation requires a separate AppHub review and a Full Admin of that tenant (inferred). Source: [Contact Center Service Apps](https://developer.webex.com/admin/docs/contact-center-service-apps), Contact Center Service Apps > org requirements, read together with the authorization requirements section. Checked 2026-09-22.
[^50]: A newly created Webex Contact Center service app is private and can only be authorised by its creator within their own organisation; authorisation outside that organisation requires manual review through Webex AppHub submission. Source: [Contact Center Service Apps](https://developer.webex.com/admin/docs/contact-center-service-apps), Contact Center Service Apps > org requirements, private visibility and cross-org authorization. Checked 2026-09-22.
[^51]: Cisco directs developers working in a free Webex organisation to request a sandbox so they have an administrator account with which to test service apps. Source: [Contact Center Service Apps](https://developer.webex.com/admin/docs/contact-center-service-apps), Contact Center Service Apps > org requirements, sandbox access note. Checked 2026-09-22.
[^52]: A Webex Contact Center developer sandbox is provisioned with one default agent-based team. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 5 (Team). Checked 2026-09-22.
[^53]: Each Webex Developer Sandbox is limited to a maximum of 10 account users, for validation and test purposes only. Source: [Webex Developer Sandbox Guide](https://developer.webex.com/admin/docs/developer-sandbox-guide), Webex Developer Sandbox Guide > Do I need a Developer Sandbox?, limitation note. Checked 2026-09-22.
[^54]: Cisco instructs developers to use the expiration values returned by the service rather than assuming a fixed token lifetime. Source: [Webex Contact Center - Authentication](https://developer.webex.com/webex-contact-center/docs/authentication), Authentication > Token Management. Checked 2026-09-22.
[^55]: Webex Contact Center API requests carry an access token in an Authorization HTTP header, and three token types are supported: personal access tokens, bot tokens and OAuth tokens issued to an Integration. Source: [Webex Contact Center - Getting Started](https://developer.webex.com/webex-contact-center/docs/getting-started), Getting Started > Accounts and Authentication. Checked 2026-09-22.
[^56]: A Webex Contact Center developer sandbox is provisioned with two default Contact Center users: a premium agent with Agent Desktop functions only, and a supervisor with additional supervisory metrics and functions. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 4 (Agents/Users). Checked 2026-09-22.
[^57]: A Webex Contact Center developer sandbox is issued two PSTN numbers: a main number assigned to the default Webex Calling location, and an entry point number assigned to the Contact Center default inbound entry point. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Provisioning Email > Two PSTN Numbers. Checked 2026-09-22.
[^58]: A Webex Contact Center developer sandbox is provisioned with five pre-configured user profiles: Administrator Only Profile, Administrator Profile, Premium Agent User Profile, Standard Agent User Profile and Supervisor Profile. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, item 7 (User profiles). Checked 2026-09-22.
[^59]: All Webex Contact Center developer sandboxes have a validity period of 180 days. Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Introduction, boldfaced NOTE above 'Sandbox Vidcasts'. Checked 2026-09-22.
[^60]: The documented contents of a Webex Contact Center developer sandbox cover voice only; no digital channel, outbound campaign, workforce optimisation or AI capability is listed as preprovisioned (inferred). Source: [Contact Center Sandbox](https://developer.webex.com/webex-contact-center/docs/sandbox_cc), Contact Center Sandbox > Sandbox Contents, items 1 to 11 read as a whole. Checked 2026-09-22.