Log inSign up
Home
Webex Connect (CPaaS)
  • Webex Connect Platform Overview
  • API REFERENCE

Webex Connect (CPaaS)

API Endpoints and Regions

Use the API base URL associated with the API family and the region in which your organization is hosted.

anchorSelect the correct endpoint

anchor

The Webex Developer Portal is globally available, but your organization and its assets are hosted regionally. The operation in the API Reference displays the base URL and version supported for the selected environment.

Digital Channel Onboarding APIs

For Digital Channel Onboarding APIs, use the following base URL for the region in which your organization is hosted:

RegionEnvironmentDigital Channel Onboarding API base URL
Irelandprodeu2https://assetmanagement.eu.webexconnect.io/connectapi
Oregonprodus1https://assetmanagement.us.webexconnect.io/connectapi
Londonprodeu1https://assetmanagement.uk.webexconnect.io/connectapi
Canadaprodca1https://assetmanagement.ca.webexconnect.io/connectapi
Sydneyprodanz1https://assetmanagement.au.webexconnect.io/connectapi
Singaporeprodsg1https://assetmanagement.sg.webexconnect.io/connectapi
Indiaprodind1https://assetmanagement.in.webexconnect.io/connectapi
Japanprodjp1https://assetmanagement.au.webexconnect.io/connectapi

The Sydney and Japan environments currently use the same Digital Channel Onboarding API base URL.

Do not construct a Digital Channel Onboarding API hostname by copying the hostname used by another Webex Connect API family. Use the complete base URL shown for the Digital Channel Onboarding operation and keep it configurable in your application.

anchorBuild a request URL

anchor

Combine the base URL shown in the API Reference with the operation path. For example, the Email create operation uses this path:

<digital-channel-onboarding-api-base-url>/v2/digital/app?channel=email

Use HTTPS and preserve the host, API version, path, and channel value exactly as documented.

anchorOrganization routing

anchor

Digital Channel Onboarding requests require the organization identifier in the x-organization-id header:

x-organization-id: <organization-id>

anchorNext steps

anchor
  • Access the API
  • Authentication
In This Article
  • Select the correct endpoint
  • Build a request URL
  • Organization routing
  • Next steps

Connect

Support

Developer Community

Developer Events

Contact Sales

Handy Links

Webex Ambassadors

Webex App Hub

Resources

Open Source Bot Starter Kits

Download Webex

DevNet Learning Labs

Terms of Service

Privacy Policy

Cookie Policy

Trademarks

© 2026 Cisco and/or its affiliates. All rights reserved.