Webex Location Call Settings API

openapi: 3.0.0
info:
  title: Webex Admin Address Book Location Call Settings API
  version: 1.0.0
  description: The Webex Admin APIs provide comprehensive programmatic access to administrative functions for managing Webex organizations, users, licenses, and settings. These APIs enable automation of user provisioning, license assignment, compliance management, and audit event retrieval. Administrators can integrate with enterprise identity systems, enforce security policies, monitor usage, and streamline onboarding/offboarding processes. The APIs support granular control over organizational resources, making them ideal for large-scale deployments and custom admin tooling.
tags:
- name: Location Call Settings
paths:
  /telephony/config/premisePstn/dialPlans/{dialPlanId}/dialPatterns:
    get:
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                type: object
                required:
                - dialPatterns
                properties:
                  dialPatterns:
                    type: array
                    items:
                      type: string
                    description: Array of dial patterns. An enterprise dial pattern is represented by a sequence of digits (1-9), followed by optional wildcard characters.
              example:
                dialPatterns: []
        '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 List of Dial Patterns
      operationId: Read the List of Dial Patterns
      description: 'List all Dial Patterns for the organization.


        Dial plans route calls to on-premises destinations by use of trunks or route groups.

        They are configured globally for an enterprise and apply to all users, regardless of location.

        A dial plan also specifies the routing choice (trunk or route group) for calls that match any of its dial patterns.

        Specific dial patterns can be defined as part of your dial plan.


        Retrieving this list requires a full or read-only administrator auth token with a scope of `spark-admin:telephony_config_read`.'
      tags:
      - Location Call Settings
      parameters:
      - name: dialPlanId
        in: path
        description: ID of the dial plan.
        required: true
        example: Y2lzY29zcGFyazovL3VzL0RJQUxfUExBTi8wNTlhMjczZS1iYmIwLTExZWMtODQyMi0wMjQyYWMxMjAwMDI
        schema:
          type: string
      - name: orgId
        in: query
        description: ID of the organization to which the dial patterns belong.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
      - name: dialPattern
        in: query
        description: 'An enterprise dial pattern is represented by a sequence of digits (1-9), followed by optional wildcard characters.

          Valid wildcard characters are `!` (matches any sequence of digits) and `X` (matches a single digit, 0-9).

          The `!` wildcard can only occur once at the end and only in an E.164 pattern

          '
        example: '+5555'
        schema:
          type: string
      - name: max
        in: query
        description: Limit the number of objects returned to this maximum count.
        example: '5'
        schema:
          type: number
      - name: start
        in: query
        description: Start at the zero-based offset in the list of matching objects.
        example: '0'
        schema:
          type: number
      - name: order
        in: query
        description: 'Order the dial patterns according to the designated fields.  Available sort fields: `dialPattern`.'
        example: dialPattern-desc
        schema:
          type: string
  /telephony/config/locations:
    get:
      responses:
        '200':
          description: OK
          headers:
            Link:
              schema:
                type: string
          content:
            application/json:
              schema:
                type: object
                required:
                - locations
                properties:
                  locations:
                    type: array
                    items:
                      $ref: '#/components/schemas/ListLocationObject'
                    description: Array of locations.
              example:
                locations:
                - id: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OL2YyZmUzOGVkLTNmNGYtNGI1NC04M2YzLTk4MDg3MWQzMjM5Yw
                  name: Denver
                  routingPrefix: '3'
                  outsideDialDigit: '1258'
                  callingLineId:
                    phoneNumber: '+12145556985'
                  e911SetupRequired: false
                  enforceOutsideDialDigit: true
                - id: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzljYzc0NDgxLTk3ZjAtNDA1NS1iYTIxLWE0NDBkMjUzZTc3OA
                  name: Denver-2
                  routingPrefix: '234'
                  outsideDialDigit: '12'
                  callingLineId:
                    name: Denver Incoming
                    phoneNumber: null
                  e911SetupRequired: false
                  enforceOutsideDialDigit: 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: List Locations Webex Calling Details
      operationId: List Locations Webex Calling Details
      description: 'Lists Webex Calling locations for an organization with Webex Calling details.


        Searching and viewing locations with Webex Calling details in your

        organization require an administrator auth token with the

        `spark-admin:telephony_config_read` scope.'
      tags:
      - Location Call Settings
      parameters:
      - name: orgId
        in: query
        description: List locations for this organization.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
      - name: max
        in: query
        description: Limit the maximum number of locations in the response.
        example: '100'
        schema:
          type: number
      - name: start
        in: query
        description: Specify the offset from the first result that you want to fetch.
        example: '0'
        schema:
          type: number
      - name: name
        in: query
        description: List locations whose name contains this string.
        example: Denver
        schema:
          type: string
      - name: order
        in: query
        description: Sort the list of locations based on `name`, either asc or desc.
        example: name-asc
        schema:
          type: string
    post:
      responses:
        '201':
          description: Created
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/LocationCallingResponseWithId'
              example:
                id: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzljYTNhZmQ3LTE5MjYtNGQ0ZS05ZDA3LTk5ZDJjMGU4OGFhMA
        '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: Enable a Location for Webex Calling
      operationId: Enable a Location for Webex Calling
      description: 'Enable a location by adding it to Webex Calling. This add Webex Calling support to a

        location created created using the POST /v1/locations API.


        Locations are used to support calling features which can be defined at the location level.


        This API requires a full administrator auth token with a scope of `spark-admin:telephony_config_write`.'
      tags:
      - Location Call Settings
      parameters:
      - name: orgId
        in: query
        description: ID of the organization in which the person resides. Only admin users of another organization (such as partners) may use this parameter as the default is the same organization as the token used to access API.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
      requestBody:
        content:
          application/json:
            example:
              id: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OLzhmZjMwMjg5LWVhMzMtNDc1Ny1iMTBmLWQ2MWIyNzFhMDVlZg
              name: Denver
              timeZone: America/Chicago
              announcementLanguage: fr_fr
              preferredLanguage: en_us
              address:
                address1: 771 Alder Drive
                address2: Cisco Site 5
                city: Milpitas
                state: CA
                postalCode: '95035'
                country: US
            schema:
              $ref: '#/components/schemas/PostLocationCallingRequest'
  /telephony/config/locations/{locationId}:
    get:
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetTelephonyLocationObject'
              example:
                id: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OL2M5N2VlMDQ5LTM1OWItNGM3OC04NDU0LTA1OGMyZWRlMjU2Mw
                name: Denver
                announcementLanguage: fr_fr
                routingPrefix: '2'
                callingLineId:
                  name: Denver Incoming
                  phoneNumber: '+12145555698'
                connection:
                  type: TRUNK
                  id: Y2lzY29zcGFyazovL3VzL1RSVU5LL2M1MGIxZjY2LTRjODMtNDAzNy04NjM1LTg2ZjlkM2VkZDQ5MQ
                subscriptionId: trial
                externalCallerIdName: Big Corp-Denver
                userLimit: 500000
                outsideDialDigit: '12'
                pAccessNetworkInfo: Richardson-TX
                defaultDomain: 98079822.int10.bcld.webex.com
                chargeNumber: '+14158952369'
                enforceOutsideDialDigit: true
                useChargeNumberForPChargeInfo: true
        '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 Webex Calling Details
      operationId: Get Location Webex Calling Details
      description: 'Shows Webex Calling details for a location, by ID.


        Specifies the location ID in the locationId parameter in the URI.


        Searching and viewing locations in your organization requires an administrator auth token with the spark-admin:telephony_config_read scope.'
      tags:
      - Location Call Settings
      parameters:
      - name: locationId
        in: path
        description: Retrieve Webex Calling location attributes for this location.
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OL2E4NjczZDIwLWM0M2EtNDQ5Ni1iYWIxLTNiMjhhZGJjMjViYQ
        schema:
          type: string
      - name: orgId
        in: query
        description: Retrieve Webex Calling location attributes for this organization.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
    put:
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/LocationPUTResponse'
              example:
                batchJobId: Y2lzY29zcGFyazovL3VzL0pPQl9JRC8wOThmNTg5MC05MTA4LTQ0YWMtODIxMy1lYmE4MGI4YzJkMjA
        '204':
          description: No Content
          headers: {}
          content: {}
        '206':
          description: Partial Content
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/LocationPUTResponse'
              example:
                failureReason: 'UpdateRoutingPrefix batch job not triggered for Location: c7e4wasdfgjfec5c52. OldRoutingPrefix : 111. NewRoutingPrefix: 212.'
        '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.'
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/LocationPUTResponse'
              example:
                failureReason: UpdateRoutingPrefixJob failed as another one is already in progress.
        '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 Webex Calling Details
      operationId: Update Location Webex Calling Details
      description: 'Update Webex Calling details for a location, by ID.


        Specifies the location ID in the `locationId` parameter in the URI.


        Modifying the `connection` via API is only supported for the local PSTN types of `TRUNK` and `ROUTE_GROUP`.


        Updating a location in your organization requires an administrator auth token with the `spark-admin:telephony_config_write` scope.'
      tags:
      - Location Call Settings
      parameters:
      - name: locationId
        in: path
        description: Updating Webex Calling location attributes for this location.
        required: true
        example: Y2lzY29zcGFyazovL3VzL0xPQ0FUSU9OL2E4NjczZDIwLWM0M2EtNDQ5Ni1iYWIxLTNiMjhhZGJjMjViYQ
        schema:
          type: string
      - name: orgId
        in: query
        description: Updating Webex Calling location attributes for this organization.
        example: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
        schema:
          type: string
      requestBody:
        content:
          application/json:
            example:
              announcementLanguage: fr_fr
              outsideDialDigit: '12'
              routingPrefix: '212'
              callingLineId:
                name: Denver Incoming
                phoneNumber: '+12145555698'
              connection:
                type: TRUNK
                id: Y2lzY29zcGFyazovL3VzL1RSVU5LL2M1MGIxZjY2LTRjODMtNDAzNy04NjM1LTg2ZjlkM2VkZDQ5MQ
              externalCallerIdName: Big Corp-Denver
              pAccessNetworkInfo: Richardson-TX
              chargeNumber: '+14158952369'
              enforceOutsideDialDigit: true
            schema:
              $ref: '#/components/schemas/PutTelephonyLocationObject'
  /telephony/config/jobs/updateRoutingPrefix:
    get:
      responses:
        '200':
          description: OK
          headers: {}
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/BatchResponse'
              example:
                items:
                - id: Y2lzY29zcGFyazovL3VzL0pPQl9JRC81YWE1NWZjNC1lNTYwLTQ3MWQtOGZhZS0yNDc3NDM3MDNkNmI
                  trackingId: NA_e82bec92-7a6c-48e5-9511-bfe4da78396e
                  sourceUserId: Y2lzY29zcGFyazovL3VzL1BFT1BMRS85OThhMThhYi1kZjY5LTQ5MWYtYmViZi03MzUxMGE3ODI5N2I
                  sourceCustomerId: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
                  targetCustomerId: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
                  instanceId: 1
                  jobExecutionStatus:
                  - id: 1
                    startTime: '2023-08-16T18:30:20.901Z'
                    endTime: '2023-08-16T18:30:34.793Z'
                    lastUpdated: '2023-08-16T18:30:36.631Z'
                    statusMessage: COMPLETED
                    exitCode: COMPLETED
                    createdTime: '2023-08-16T18:30:20.882Z'
                    stepExecutionStatuses:
                    - id: 2
                      startTime: '2023-08-16T18:30:20.970Z'
                      endTime: '2023-08-16T18:30:22.801Z'
                      lastUpdated: '2023-08-16T18:30:22.801Z'
                      statusMessage: COMPLETED
                      exitCode: COMPLETED
                      name: updateroutingprefixPreProcessMemberData
                      timeElapsed: PT1.831S
                    - id: 3
                      startTime: '2023-08-16T18:30:22.811Z'
                      endTime: '2023-08-16T18:30:26.022Z'
                      lastUpdated: '2023-08-16T18:30:26.022Z'
                      statusMessage: COMPLETED
                      exitCode: COMPLETED
                      name: updateroutingprefixGenerateUserReport
                      timeElapsed: PT3.211S
                    - id: 4
                      startTime: '2023-08-16T18:30:26.032Z'
                      endTime: '2023-08-16T18:30:26.538Z'
                      lastUpdated: '2023-08-16T18:30:26.538Z'
                      statusMessage: COMPLETED
                      exitCode: COMPLETED
                      name: updateroutingprefixPreProcessCiUserData
                      timeElapsed: PT0.506S
                    - id: 5
                      startTime: '2023-08-16T18:30:26.549Z'
                      endTime: '2023-08-16T18:30:29.907Z'
                      lastUpdated: '2023-08-16T18:30:29.907Z'
                      statusMessage: COMPLETED
                      exitCode: COMPLETED
                      name: updateroutingprefixGenerateMachineAccountReport
                      timeElapsed: PT3.358S
                    - id: 6
                      startTime: '2023-08-16T18:30:29.916Z'
                      endTime: '2023-08-16T18:30:30.007Z'
                      lastUpdated: '2023-08-16T18:30:30.007Z'
                      statusMessage: COMPLETED
                      exitCode: COMPLETED
                      name: updateroutingprefixPreProcessCiMachineAccountData
                      timeElapsed: PT0.091S
                    - id: 7
                      startTime: '2023-08-16T18:30:30.018Z'
                      endTime: '2023-08-16T18:30:34.447Z'
                      lastUpdated: '2023-08-16T18:30:34.447Z'
                      statusMessage: COMPLETED
                      exitCode: COMPLETED
                      name: updateroutingprefixFetchVONExtensions
                      timeElapsed: PT4.429S
                    - id: 8
                      startTime: '2023-08-16T18:30:34.466Z'
                      endTime: '2023-08-16T18:30:34.789Z'
                      lastUpdated: '2023-08-16T18:30:34.789Z'
                      statusMessage: COMPLETED
                      exitCode: COMPLETED
                      name: updateroutingprefixUpdateRoutingPrefix
                      timeElapsed: PT0.323S
                    timeElapsed: PT13.749S
                  latestExecutionStatus: COMPLETED
                  latestExecutionExitCode: COMPLETED
                  counts:
                    routingPrefixFailed: 0
                    routingPrefixUpdated: 7
                - id: Y2lzY29zcGFyazovL3VzL0pPQl9JRC9mZmU3MmVhMS1mMzBhLTQ4MDEtYjA1ZC1mNDQzM2IyZThiZDE
                  trackingId: NA_2688c70a-1887-443d-800b-7efe9cca346f
                  sourceUserId: Y2lzY29zcGFyazovL3VzL1BFT1BMRS85OThhMThhYi1kZjY5LTQ5MWYtYmViZi03MzUxMGE3ODI5N2I
                  sourceCustomerId: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
                  targetCustomerId: Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE
                  instanceId: 0
                  jobExecutionStatus:
                  - id: 0
                    startTime: '2023-08-16T18:27:44.392Z'
                    endTime: '2023-08-16T18:28:00.474Z'
                    lastUpdated: '2023-08-16T18:28:02.621Z'
                    statusMessage: FAILED
                    exitCode: FAILED
                    createdTime: '2023-08-16T18:27:44.341Z'
                    stepExecutionStatuses:
                    - id: 0
                      startTime: '2023-08-16T18:27:56.083Z'
                      endTime: '2023-08-16T18:27:58.294Z'
                      lastUpdated: '2023-08-16T18:27:58.294Z'
                      statusMessage: COMPLETED
                      exitCode: COMPLETED
                      name: updateroutingprefixPreProcessMemberData
                      timeElapsed: PT2.211S
                    - id: 1
                      startTime: '2023-08-16T18:27:58.305Z'
                      endTime: '2023-08-16T18:28:00.469Z'
                      lastUpdated: '2023-08-16T18:28:00.469Z'
                      statusMessage: FAILED
                      exitCode: FAILED
                      name: updateroutingprefixGenerateUserReport
                      timeElapsed: PT2.164S
                    timeElapsed: PT4.375S
              

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