How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Webex

Webex Location Call Settings: Call Handling API

The Location Call Settings: Call Handling API from Webex — 8 operation(s) for location call settings: call handling.

Documentation Provider Profile APIs.io OpenAPI GitHub

Webex Location Call Settings: Call Handling API is one of 193 APIs that Webex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Location Call Settings: Call Handling. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 19 operations across 8 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

19 operations 8 paths 20 schemas 3 DELETE7 GET3 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Authentication
OAuth 2.0, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 3

Webex Location Call Settings: Call Handling API declares 3 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow. It accepts HTTP bearer tokens (JWT) (bearer-key). It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearer-key — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • bearerAuth — e.g. Bearer YOURAUTHORIZATIONTOKEN

Paths & Operations 19

Across 8 paths, the API surfaces 19 operations — 3 DELETE, 7 GET, 3 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Location Call Settings: Call Handling 19
POST
/telephony/config/locations/{locationId}/actions/generatePassword/invoke
Generate example password for Location
Generate example password for Location 2 params body → 200400401403404405409410
GET
/telephony/config/locations/{locationId}/internalDialing
Read the Internal Dialing configuration for a location
Read the Internal Dialing configuration for a location 2 params → 200400401403404405409410
PUT
/telephony/config/locations/{locationId}/internalDialing
Modify the Internal Dialing configuration for a location
Modify the Internal Dialing configuration for a location 2 params body → 204400401403404405409410
GET
/telephony/config/locations/{locationId}/intercept
Get Location Intercept
Get Location Intercept 2 params → 200400401403404405409410
PUT
/telephony/config/locations/{locationId}/intercept
Put Location Intercept
Put Location Intercept 2 params body → 204400401403404405409410
GET
/telephony/config/locations/{locationId}/outgoingPermission
Get Location Outgoing Permission
Get Location Outgoing Permission 2 params → 200400401403404405409410
PUT
/telephony/config/locations/{locationId}/outgoingPermission
Update Location Outgoing Permission
Update Location Outgoing Permission 2 params body → 204400401403404405409410
GET
/telephony/config/locations/{locationId}/outgoingPermission/autoTransferNumbers
Get Outgoing Permission Auto Transfer Number
Get Outgoing Permission Auto Transfer Number 2 params → 200400401403404405409410
PUT
/telephony/config/locations/{locationId}/outgoingPermission/autoTransferNumbers
Put Outgoing Permission Auto Transfer Number
Put Outgoing Permission Auto Transfer Number 2 params body → 204400401403404405409410
GET
/telephony/config/locations/{locationId}/outgoingPermission/accessCodes
Get Outgoing Permission Location Access Code
Get Outgoing Permission Location Access Code 2 params → 200400401403404405409410
POST
/telephony/config/locations/{locationId}/outgoingPermission/accessCodes
Create Outgoing Permission a new access code for a customer location
Create Outgoing Permission a new access code for a customer location 2 params body → 201400401403404405409410
PUT
/telephony/config/locations/{locationId}/outgoingPermission/accessCodes
Delete Outgoing Permission Access Code Location
Delete Outgoing Permission Access Code Location 2 params body → 204400401403404405409410
DELETE
/telephony/config/locations/{locationId}/outgoingPermission/accessCodes
Delete all Outgoing Permission Access Code for a Location
Delete all Outgoing Permission Access Code for a Location 2 params → 204400401403404405409410
GET
/telephony/config/locations/{locationId}/outgoingPermission/digitPatterns
Get Outgoing Permission Digit Pattern for a Location
Get Outgoing Permission Digit Pattern for a Location 2 params → 200400401403404405409410
POST
/telephony/config/locations/{locationId}/outgoingPermission/digitPatterns
Create Outgoing Permission a new Digit Pattern for a location
Create Outgoing Permission a new Digit Pattern for a location 2 params body → 201400401403404405409410
DELETE
/telephony/config/locations/{locationId}/outgoingPermission/digitPatterns
Delete all Outgoing Permission Digit Patterns for a Location
Delete all Outgoing Permission Digit Patterns for a Location 2 params → 204400401403404405409410
GET
/telephony/config/locations/{locationId}/outgoingPermission/digitPatterns/{digitPatternId}
Get Details for a Outgoing Permission Digit Pattern for a Location
Get Details for a Outgoing Permission Digit Pattern for a Location 3 params → 200400401403404405409410
PUT
/telephony/config/locations/{locationId}/outgoingPermission/digitPatterns/{digitPatternId}
Update a Outgoing Permission Digit Pattern for a Location
Update a Outgoing Permission Digit Pattern for a Location 3 params body → 204400401403404405409410
DELETE
/telephony/config/locations/{locationId}/outgoingPermission/digitPatterns/{digitPatternId}
Delete a Outgoing Permission Digit Pattern for a Location
Delete a Outgoing Permission Digit Pattern for a Location 3 params → 204400401403404405409410

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are LocationDigitPatternObject (5 properties), LocationOutgoingPermissionDigitPatternPatchObject (4 properties), LocationOutgoingPermissionDigitPatternPostObject (4 properties), CallingPermissionObject (4 properties). Each schema is shown below with its type and property counts.

CallingPermissionObject
object
4 properties 4 required
LocationOutgoingPermissionDigitPatternPatchObject
object
4 properties
PostLocationAccessCodeObject
object
1 property
RouteType
string
ROUTEGROUP - Route group must include at least one trunk with a maximum of 10 trunks per route group. TRUNK - Connection between Webex Calling and the premises.
GetAutoTransferNumberObject
object
3 properties
GetLocationInterceptObject
object
3 properties 1 required
LocationOutgoingPermissionDigitPatternPostObject
object
4 properties 4 required
RouteIdentity
object
3 properties 3 required
InternalDialingPut
object
2 properties
InternalDialingGet
object
2 properties
PutLocationInterceptObject
object
3 properties 1 required
CallingPermissionPatchObject
object
3 properties 3 required
LocationOutgoingPermissionDigitPatternGetListObject
object
1 property 1 required
PutAutoTransferNumberObject
object
3 properties
UnknownExtensionRouteIdentity
object
2 properties 2 required
GetLocationAccessCodeObject
object
1 property
GeneratePasswordPostResponse
object
1 property
PutAccessCodeLocationObject
object
1 property 1 required
LocationDigitPatternObject
object
5 properties 5 required
PasswordGenerate
string
sip - SIP password setting

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-location-call-settings-call-handling-api-openapi.yml Raw ↑

Other APIs Webex publishes across the network.

Webex Address Book API
AE Profile APIs.io
Webex Admin Audit Events API
AE Profile APIs.io
Webex Agent Personal Greeting Files API
AE Profile APIs.io
Webex Agent Summaries API
AE Profile APIs.io
Webex Agent Wellbeing API
AE Profile APIs.io
Webex Agents API
AE Profile APIs.io
Webex AI Feature API
AE Profile APIs.io
Webex API - Domain Management API
AE Profile APIs.io
Webex Archive Users API
AE Profile APIs.io
Webex Attachment Actions API
AE Profile APIs.io
Webex Audio Files API
AE Profile APIs.io
Webex Authorizations API
AE Profile APIs.io
#Location Call Settings: Call Handling
← Back to W APIs
API Details
ID
webex:webex-location-call-settings-call-handling-api
Docs
https://developer.webex.com/docs/messaging
Provider
Webex
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=webex-location-call-settings-call-handling-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/webex-location-call-settings-call-handling-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Webex Location Call Settings: Call Handling API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.