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.

Operations 19

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

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/webex-location-call-settings-call-handling-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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

OpenAPI Specification

webex-location-call-settings-call-handling-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: 'Webex Location Call Settings: Call Handling API'
  version: 1.0.0
  description: 'Operations tagged Location Call Settings: Call Handling across 2 of this provider''s published API definitions: webex-cloud-calling-openapi.json, webex-location-call-settings-call-handling-api-openapi.yml. Each path carries the servers of the definition it was published in.'
  x-provenance:
    method: harvested
    authored_by: Cisco Webex
    harvested_by: API Evangelist
    harvested_on: '2026-08-19'
    first_party: true
    note: Published by Cisco. Retrieved unmodified except for this x-provenance block.
    provider_published: true
    derived_view: Per-tag view of webex-cloud-calling-openapi.json, the provider's source document. Operations and schemas are the provider's, unmodified; only the partition is ours.
    derived_from: webex-cloud-calling-openapi.json
    operation_coverage: 19/19
  x-evidence:
  - type: source
    url: https://github.com/webex/webex-openapi-specs/blob/main/public-spec/webex-cloud-calling.json
  - type: raw
    url: https://raw.githubusercontent.com/webex/webex-openapi-specs/main/public-spec/webex-cloud-calling.json
tags:
- name: 'Location Call Settings: Call Handling'
paths:
  /telephony/config/locations/{locationId}/actions/generatePassword/invoke:
    post:
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GeneratePasswordPostResponse'
              example:
                exampleSipPassword: xyz123!
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message will explain further.'
        '401':
          description: 'Unauthorized: Authentication credentials were missing or incorrect.'
        '403':
          description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
        '404':
          description: 'Not Found: The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.'
        '405':
          description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
        '409':
          description: 'Conflict: The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.'
        '410':
          description: 'Gone: The requested resource is no longer available.'
        '415':
          description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used a media type that is not supported.'
        '423':
          description: 'Locked: The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again.'
        '428':
          description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
        '429':
          description: 'Too Many Requests: Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made.'
        '500':
          description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact the [Webex Developer Support team](/explore/support).'
        '502':
          description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the request. Try again later.'
        '503':
          description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
        '504':
          description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it.'
      summary: Generate example password for Location
      operationId: Generate example password for Location
      description: 'Generates an example password using the effective password settings for the location. If you don''t specify anything in the `generate` field or don''t provide a request body, then you will receive a SIP password by default.


        Used while creating a trunk and shouldn''t be used anywhere else.


        Generating an example password requires a full or write-only administrator or location administrator auth token with a scope of `spark-admin:telephony_config_write`.'
      tags:
      - 'Location Call Settings: Call Handling'
      parameters:
      - name: locationId
        in: path
        description: Location for which example password has to be generated.
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzFkNjAzZTljLWJmM2QtNDA5OS05MGFiLTkyZWFlZWE3MjEzNw
        schema:
          type: string
      - name: orgId
        in: query
        description: Organization to which the location belongs.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
      requestBody:
        content:
          application/json:
            example:
              generate:
              - sip
            schema:
              type: object
              properties:
                generate:
                  type: array
                  items:
                    $ref: '#/components/schemas/PasswordGenerate'
                  description: password settings array.
  /telephony/config/locations/{locationId}/internalDialing:
    get:
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InternalDialingGet'
              example:
                enableUnknownExtensionRoutePolicy: true
                unknownExtensionRouteIdentity:
                  id: Y2lzY29zcGFyazovL3VzL1JPVVRFX0dST1VQLzA1OWEyNzNlLWJiYjAtMTFlYy04NDIyLTAyNDJhYzEyMDAwMg
                  name: route_identity_name
                  type: ROUTE_GROUP
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message will explain further.'
        '401':
          description: 'Unauthorized: Authentication credentials were missing or incorrect.'
        '403':
          description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
        '404':
          description: 'Not Found: The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.'
        '405':
          description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
        '409':
          description: 'Conflict: The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.'
        '410':
          description: 'Gone: The requested resource is no longer available.'
        '415':
          description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used a media type that is not supported.'
        '423':
          description: 'Locked: The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again.'
        '428':
          description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
        '429':
          description: 'Too Many Requests: Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made.'
        '500':
          description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact the [Webex Developer Support team](/explore/support).'
        '502':
          description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the request. Try again later.'
        '503':
          description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
        '504':
          description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it.'
      summary: Read the Internal Dialing configuration for a location
      operationId: Read the Internal Dialing configuration for a location
      description: 'Get current configuration for routing unknown extensions to the Premises as internal calls


        If some users in a location are registered to a PBX, retrieve the setting to route unknown extensions (digits that match the extension length) to the PBX.


        Retrieving the internal dialing configuration requires a full or read-only administrator or location administrator auth token with a scope of `spark-admin:telephony_config_read`.'
      tags:
      - 'Location Call Settings: Call Handling'
      parameters:
      - name: locationId
        in: path
        description: location for which internal calling configuration is being requested
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzUyOTA4Mg
        schema:
          type: string
      - name: orgId
        in: query
        description: List route identities for this organization.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
    put:
      responses:
        '204':
          description: No Content
          headers: {}
          content: {}
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message will explain further.'
        '401':
          description: 'Unauthorized: Authentication credentials were missing or incorrect.'
        '403':
          description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
        '404':
          description: 'Not Found: The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.'
        '405':
          description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
        '409':
          description: 'Conflict: The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.'
        '410':
          description: 'Gone: The requested resource is no longer available.'
        '415':
          description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used a media type that is not supported.'
        '423':
          description: 'Locked: The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again.'
        '428':
          description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
        '429':
          description: 'Too Many Requests: Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made.'
        '500':
          description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact the [Webex Developer Support team](/explore/support).'
        '502':
          description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the request. Try again later.'
        '503':
          description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
        '504':
          description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it.'
      summary: Modify the Internal Dialing configuration for a location
      operationId: Modify the Internal Dialing configuration for a location
      description: 'Modify current configuration for routing unknown extensions to the premise as internal calls


        If some users in a location are registered to a PBX, enable the setting to route unknown extensions (digits that match the extension length) to the PBX.


        Editing the internal dialing configuration requires a full administrator or location administrator auth token with a scope of `spark-admin:telephony_config_write`.'
      tags:
      - 'Location Call Settings: Call Handling'
      parameters:
      - name: locationId
        in: path
        description: location for which internal calling configuration is being requested
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzUyOTA4Mg
        schema:
          type: string
      - name: orgId
        in: query
        description: List route identities for this organization.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/InternalDialingPut'
  /telephony/config/locations/{locationId}/intercept:
    get:
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetLocationInterceptObject'
              example:
                enabled: true
                incoming:
                  type: INTERCEPT_ALL
                  voicemailEnabled: false
                  announcements:
                    greeting: DEFAULT
                    fileName: audiofile.wav
                    newNumber:
                      enabled: true
                      destination: '2147691003'
                    zeroTransfer:
                      enabled: true
                      destination: '2147691005'
                outgoing:
                  type: ALLOW_LOCAL_ONLY
                  transferEnabled: true
                  destination: '2147691007'
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message will explain further.'
        '401':
          description: 'Unauthorized: Authentication credentials were missing or incorrect.'
        '403':
          description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
        '404':
          description: 'Not Found: The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.'
        '405':
          description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
        '409':
          description: 'Conflict: The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.'
        '410':
          description: 'Gone: The requested resource is no longer available.'
        '415':
          description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used a media type that is not supported.'
        '423':
          description: 'Locked: The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again.'
        '428':
          description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
        '429':
          description: 'Too Many Requests: Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made.'
        '500':
          description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact the [Webex Developer Support team](/explore/support).'
        '502':
          description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the request. Try again later.'
        '503':
          description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
        '504':
          description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it.'
      summary: Get Location Intercept
      operationId: Get Location Intercept
      description: 'Retrieve intercept location details for a customer location.


        Intercept incoming or outgoing calls for persons in your organization. If this is enabled, calls are either routed to a designated number the person chooses, or to the person''s voicemail.


        Retrieving intercept location details requires a full, user or read-only administrator or location administrator auth token with a scope of `spark-admin:telephony_config_read`.'
      tags:
      - 'Location Call Settings: Call Handling'
      parameters:
      - name: locationId
        in: path
        description: Retrieve intercept details for this location.
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzMxMTYx
        schema:
          type: string
      - name: orgId
        in: query
        description: Retrieve intercept location details for a customer location.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
    put:
      responses:
        '204':
          description: No Content
          headers: {}
          content: {}
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message will explain further.'
        '401':
          description: 'Unauthorized: Authentication credentials were missing or incorrect.'
        '403':
          description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
        '404':
          description: 'Not Found: The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.'
        '405':
          description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
        '409':
          description: 'Conflict: The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.'
        '410':
          description: 'Gone: The requested resource is no longer available.'
        '415':
          description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used a media type that is not supported.'
        '423':
          description: 'Locked: The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again.'
        '428':
          description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
        '429':
          description: 'Too Many Requests: Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made.'
        '500':
          description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact the [Webex Developer Support team](/explore/support).'
        '502':
          description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the request. Try again later.'
        '503':
          description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
        '504':
          description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it.'
      summary: Put Location Intercept
      operationId: Put Location Intercept
      description: 'Modifies the intercept location details for a customer location.


        Intercept incoming or outgoing calls for users in your organization. If this is enabled, calls are either routed to a designated number the user chooses, or to the user''s voicemail.


        Modifying the intercept location details requires a full, user administrator or location administrator auth token with a scope of `spark-admin:telephony_config_write`.'
      tags:
      - 'Location Call Settings: Call Handling'
      parameters:
      - name: locationId
        in: path
        description: Modifies the intercept details for this location.
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzMxMTYx
        schema:
          type: string
      - name: orgId
        in: query
        description: Modifies the intercept location details for a customer location.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
      requestBody:
        content:
          application/json:
            example:
              enabled: true
              incoming:
                type: INTERCEPT_ALL
                voicemailEnabled: false
                announcements:
                  greeting: DEFAULT
                  fileName: audiofile.wav
                  newNumber:
                    enabled: true
                    destination: '2147691003'
                  zeroTransfer:
                    enabled: true
                    destination: '2147691005'
              outgoing:
                type: ALLOW_LOCAL_ONLY
                transferEnabled: true
                destination: '2147691007'
            schema:
              $ref: '#/components/schemas/PutLocationInterceptObject'
  /telephony/config/locations/{locationId}/outgoingPermission:
    get:
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                type: object
                properties:
                  callingPermissions:
                    type: array
                    items:
                      $ref: '#/components/schemas/CallingPermissionObject'
                    description: Array of calling permissions.
              example:
                callingPermissions:
                - callType: INTERNAL_CALL
                  action: ALLOW
                  transferEnabled: true
                  isCallTypeRestrictionEnabled: false
                - callType: TOLL_FREE
                  action: ALLOW
                  transferEnabled: true
                  isCallTypeRestrictionEnabled: false
                - callType: INTERNATIONAL
                  action: BLOCK
                  transferEnabled: false
                  isCallTypeRestrictionEnabled: true
                - callType: OPERATOR_ASSISTED
                  action: ALLOW
                  transferEnabled: true
                  isCallTypeRestrictionEnabled: false
                - callType: CHARGEABLE_DIRECTORY_ASSISTED
                  action: BLOCK
                  transferEnabled: true
                  isCallTypeRestrictionEnabled: false
                - callType: SPECIAL_SERVICES_I
                  action: ALLOW
                  transferEnabled: true
                  isCallTypeRestrictionEnabled: false
                - callType: SPECIAL_SERVICES_II
                  action: ALLOW
                  transferEnabled: true
                  isCallTypeRestrictionEnabled: false
                - callType: PREMIUM_SERVICES_I
                  action: BLOCK
                  transferEnabled: false
                  isCallTypeRestrictionEnabled: true
                - callType: PREMIUM_SERVICES_II
                  action: BLOCK
                  transferEnabled: false
                  isCallTypeRestrictionEnabled: true
                - callType: NATIONAL
                  action: ALLOW
                  transferEnabled: true
                  isCallTypeRestrictionEnabled: false
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message will explain further.'
        '401':
          description: 'Unauthorized: Authentication credentials were missing or incorrect.'
        '403':
          description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
        '404':
          description: 'Not Found: The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.'
        '405':
          description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
        '409':
          description: 'Conflict: The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.'
        '410':
          description: 'Gone: The requested resource is no longer available.'
        '415':
          description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used a media type that is not supported.'
        '423':
          description: 'Locked: The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again.'
        '428':
          description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
        '429':
          description: 'Too Many Requests: Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made.'
        '500':
          description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact the [Webex Developer Support team](/explore/support).'
        '502':
          description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the request. Try again later.'
        '503':
          description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
        '504':
          description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it.'
      summary: Get Location Outgoing Permission
      operationId: Get Location Outgoing Permission
      description: 'Retrieve the location''s outgoing call settings.


        A location''s outgoing call settings allow you to determine the types of calls the people/workspaces at the location are allowed to make, as well as configure the default calling permission for each call type at the location.


        Retrieving a location''s outgoing call settings requires a full, user or read-only administrator or location administrator auth token with a scope of spark-admin:telephony_config_read.'
      tags:
      - 'Location Call Settings: Call Handling'
      parameters:
      - name: locationId
        in: path
        description: Retrieve outgoing call settings for this location.
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzMxMTYx
        schema:
          type: string
      - name: orgId
        in: query
        description: Retrieve outgoing call settings for this organization.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
    put:
      responses:
        '204':
          description: No Content
          headers: {}
          content: {}
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served. An accompanying error message will explain further.'
        '401':
          description: 'Unauthorized: Authentication credentials were missing or incorrect.'
        '403':
          description: 'Forbidden: The request is understood, but it has been refused or access is not allowed.'
        '404':
          description: 'Not Found: The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method.'
        '405':
          description: 'Method Not Allowed: The request was made to a resource using an HTTP request method that is not supported.'
        '409':
          description: 'Conflict: The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once.'
        '410':
          description: 'Gone: The requested resource is no longer available.'
        '415':
          description: 'Unsupported Media Type: The request was made to a resource without specifying a media type or used a media type that is not supported.'
        '423':
          description: 'Locked: The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again.'
        '428':
          description: 'Precondition Required: File(s) cannot be scanned for malware and need to be force downloaded.'
        '429':
          description: 'Too Many Requests: Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made.'
        '500':
          description: 'Internal Server Error: Something went wrong on the server. If the issue persists, feel free to contact the [Webex Developer Support team](/explore/support).'
        '502':
          description: 'Bad Gateway: The server received an invalid response from an upstream server while processing the request. Try again later.'
        '503':
          description: 'Service Unavailable: Server is overloaded with requests. Try again later.'
        '504':
          description: 'Gateway Timeout: An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it.'
      summary: Update Location Outgoing Permission
      operationId: Update Location Outgoing Permission
      description: 'Update the location''s outgoing call settings.


        Location''s outgoing call settings allows you to determine the types of calls the people/workspaces at this location are allowed to make and configure the default calling permission for each call type at a location.


        Updating a location''s outgoing call settings requires a full administrator or location administrator auth token with a scope of spark-admin:telephony_config_write.'
      tags:
      - 'Location Call Settings: Call Handling'
      parameters:
      - name: locationId
        in: path
        description: Update outgoing call settings for this location.
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzMxMTYx
        schema:
          type: string
      - name: orgId
        in: query
        description: Update outgoing call settings for this o

# --- truncated at 32 KB (104 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/webex/refs/heads/main/openapi/webex-location-call-settings-call-handling-api-openapi.yml