Webex Call Settings For Me With UserHub Phase2 API

The Call Settings For Me With UserHub Phase2 API from Webex — 18 operation(s) for call settings for me with userhub phase2.

Operations 35

GET /telephony/config/people/me/settings/priorityAlert Get Priority Alert Settings #
PUT /telephony/config/people/me/settings/priorityAlert Modify Priority Alert Settings for User #
POST /telephony/config/people/me/settings/priorityAlert/criteria Add a Priority Alert Criteria #
GET /telephony/config/people/me/settings/priorityAlert/criteria/{id} Get Priority Alert Criteria Settings #
PUT /telephony/config/people/me/settings/priorityAlert/criteria/{id} Modify Settings for a Priority Alert Criteria #
DELETE /telephony/config/people/me/settings/priorityAlert/criteria/{id} Delete a Priority Alert Criteria #
GET /telephony/config/people/me/schedules Get User (and Location) Schedules #
POST /telephony/config/people/me/schedules Add a User level Schedule for Call Settings #
GET /telephony/config/people/me/schedules/{scheduleType}/{scheduleId} Get User Schedule #
PUT /telephony/config/people/me/schedules/{scheduleType}/{scheduleId} Modify User Schedule #
DELETE /telephony/config/people/me/schedules/{scheduleType}/{scheduleId} Delete a User Schedule #
POST /telephony/config/people/me/schedules/{scheduleType}/{scheduleId}/events Add an event for a User Schedule #
GET /telephony/config/people/me/schedules/{scheduleType}/{scheduleId}/events/{eventId} Get User Schedule Event #
PUT /telephony/config/people/me/schedules/{scheduleType}/{scheduleId}/events/{eventId} Modify User Schedule Event #
DELETE /telephony/config/people/me/schedules/{scheduleType}/{scheduleId}/events/{eventId} Delete User a Schedule Event #
GET /telephony/config/people/me/locations/schedules/{scheduleType}/{scheduleId} Get User's Location Level Schedule #
GET /telephony/config/people/me/settings/callNotify Get Call Notify Settings for User #
PUT /telephony/config/people/me/settings/callNotify Modify Call Notify Settings for User #
POST /telephony/config/people/me/settings/callNotify/criteria Add a Call Notify Criteria #
GET /telephony/config/people/me/settings/callNotify/criteria/{id} Get Call Notify Criteria Settings #
PUT /telephony/config/people/me/settings/callNotify/criteria/{id} Modify a Call Notify Criteria #
DELETE /telephony/config/people/me/settings/callNotify/criteria/{id} Delete a Call Notify Criteria #
GET /telephony/config/people/me/settings/selectiveAccept Get Selective Call Accept Settings for User #
PUT /telephony/config/people/me/settings/selectiveAccept Modify Selective Call Accept Settings for User #
POST /telephony/config/people/me/settings/selectiveAccept/criteria Add User Selective Call Accept Criteria #
GET /telephony/config/people/me/settings/selectiveAccept/criteria/{id} Get Selective Call Accept Criteria Settings for User #
PUT /telephony/config/people/me/settings/selectiveAccept/criteria/{id} Modify a Selective Call Accept Criteria #
DELETE /telephony/config/people/me/settings/selectiveAccept/criteria/{id} Delete a Selective Call Accept Criteria #
GET /telephony/config/people/me/location/assignedNumbers Get Available Numbers for User's Location #
POST /telephony/config/people/me/settings/selectiveForward/criteria Add a Selective Call Forwarding Criteria #
GET /telephony/config/people/me/settings/selectiveForward/criteria/{id} Get Settings for a Selective Call Forwarding Criteria #
PUT /telephony/config/people/me/settings/selectiveForward/criteria/{id} Modify Settings for a Selective Call Forwarding Criteria #
DELETE /telephony/config/people/me/settings/selectiveForward/criteria/{id} Delete a Selective Call Forwarding Criteria #
GET /telephony/config/people/me/settings/selectiveForward Get Selective Call Forward Settings for User #
PUT /telephony/config/people/me/settings/selectiveForward Modify Selective Call Forward Settings for User #

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-call-settings-for-me-with-userhub-phase2-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-call-settings-for-me-with-userhub-phase2-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Webex Call Settings For Me With UserHub Phase2 API
  version: 1.0.0
  description: 'Operations tagged Call Settings For Me With UserHub Phase2 across 2 of this provider''s published API definitions: webex-call-settings-for-me-with-userhub-phase2-api-openapi.yml, webex-cloud-calling-openapi.json. 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: 35/35
  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: Call Settings For Me With UserHub Phase2
paths:
  /telephony/config/people/me/settings/priorityAlert:
    get:
      responses:
        '200':
          description: Priority Alert Settings retrieved successfully for the authenticated user.
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PriorityAlertGet'
              example:
                enabled: false
                criteria:
                - id: Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY
                  scheduleName: CustomHoliday(Group)
                  source: ALL_NUMBERS
                  notificationEnabled: false
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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 Priority Alert Settings
      operationId: getMyPriorityAlertSettings
      description: 'Get Priority Alert Settings for the authenticated user.


        Priority alert allows you to set up a unique ringtone based on predefined criteria. This is helpful, when the user wants to be quickly notified that a specific phone number is calling.


        This API requires a user auth token with a scope of `spark:telephony_config_read`.'
      tags:
      - Call Settings For Me With UserHub Phase2
      parameters: []
    put:
      responses:
        '204':
          description: Priority Alert Settings updated successfully for the authenticated user.
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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 Priority Alert Settings for User
      operationId: updateMyPriorityAlertSettings
      description: 'Update Priority Alert Settings for the authenticated user.


        Priority alert allows you to set up a unique ringtone based on predefined criteria. This is helpful, when the user wants to be quickly notified that a specific phone number is calling.


        This API requires a user auth token with a scope of `spark:telephony_config_write`.'
      tags:
      - Call Settings For Me With UserHub Phase2
      parameters: []
      requestBody:
        content:
          application/json:
            example:
              enabled: false
            schema:
              $ref: '#/components/schemas/PriorityAlertPatch'
  /telephony/config/people/me/settings/priorityAlert/criteria:
    post:
      summary: Add a Priority Alert Criteria
      operationId: createMyPriorityAlertCriteria
      description: 'Create a Priority Alert Criteria for the authenticated user.


        Priority alert allows you to set up a unique ringtone based on predefined criteria. This is helpful, when the user wants to be quickly notified that a specific phone number is calling.


        This API requires a user auth token with a scope of `spark:telephony_config_write`.'
      tags:
      - Call Settings For Me With UserHub Phase2
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PriorityAlertCriteriaPatch'
            example:
              scheduleName: Holiday V2
              scheduleType: businessHours
              scheduleLevel: PEOPLE
              callsFrom: ANY_PHONE_NUMBER
              anonymousCallersEnabled: true
              unavailableCallersEnabled: false
              notificationEnabled: true
      responses:
        '200':
          description: Priority Alert Criteria created successfully. Returns the criteria ID.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseId'
              example:
                id: Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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.'
        '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.'
        '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.'
        '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).'
  /telephony/config/people/me/settings/priorityAlert/criteria/{id}:
    get:
      responses:
        '200':
          description: Call Priority Alert Criteria Settings retrieved for the authenticated user.
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PriorityAlertCriteriaGet'
              example:
                id: Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY
                scheduleName: CustomHoliday(Group)
                scheduleType: holidays
                scheduleLevel: PEOPLE
                callsFrom: SELECT_PHONE_NUMBERS
                anonymousCallersEnabled: false
                unavailableCallersEnabled: false
                phoneNumbers:
                - '+16177817765'
                notificationEnabled: false
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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 Priority Alert Criteria Settings
      operationId: getMyPriorityAlertCriteriaSettings
      description: 'Get Priority Alert Criteria Settings for the authenticated user.


        Priority alert allows you to set up a unique ringtone based on predefined criteria. This is helpful, when the user wants to be quickly notified that a specific phone number is calling.


        This API requires a user auth token with a scope of `spark:telephony_config_read`.'
      tags:
      - Call Settings For Me With UserHub Phase2
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
        example: Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY
        description: 'The `id` parameter specifies the unique identifier for the priority alert criteria. Example: `Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY`.'
    put:
      responses:
        '204':
          description: Priority Alert Criteria Settings updated successfully for the authenticated user.
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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 Settings for a Priority Alert Criteria
      operationId: updateMyPriorityAlertCriteriaSettings
      description: 'Modify Priority Alert Criteria Settings for the authenticated user.


        Priority alert allows you to set up a unique ringtone based on predefined criteria. This API allows modifying attributes such as name, phoneNumbers etc for a particular criteria.


        This API requires a user auth token with a scope of `spark:telephony_config_write`.'
      tags:
      - Call Settings For Me With UserHub Phase2
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
        example: Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY
        description: 'The `id` parameter specifies the unique identifier for the priority alert criteria. Example: `Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY`.'
      requestBody:
        content:
          application/json:
            example:
              scheduleName: Holiday V2
              scheduleType: holidays
              scheduleLevel: LOCATION
              callsFrom: SELECT_PHONE_NUMBERS
              anonymousCallersEnabled: true
              unavailableCallersEnabled: true
              notificationEnabled: false
              phoneNumbers:
              - '+16177817766'
            schema:
              $ref: '#/components/schemas/PriorityAlertCriteriaPatch'
    delete:
      summary: Delete a Priority Alert Criteria
      operationId: deleteMyPriorityAlertCriteria
      description: 'Delete a Priority Alert criteria for the authenticated user.


        Priority alert allows you to set up a unique ringtone based on predefined criteria. This API removes a specific criteria rule by its unique identifier.


        This API requires a user auth token with a scope of `spark:telephony_config_write`.'
      tags:
      - Call Settings For Me With UserHub Phase2
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
        example: Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY
        description: 'The `id` parameter specifies the unique identifier for the priority alert criteria. Example: `Y2lzY29zcGFyazovL3VzL0NSSVRFUklBL1oxNzU0MzgzODQzNTA5NzY`.'
      responses:
        '204':
          description: Priority Alert criteria deleted successfully. No content is returned.
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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.'
        '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).'
  /telephony/config/people/me/schedules:
    get:
      responses:
        '200':
          description: Schedules retrieved successfully for the authenticated user.
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserScheduleListGetResponse'
              example:
                schedules:
                - id: Y2lzY29zcGFyazovL3VzL1VTRVJfU0NIRURVTEUvVTJOb1pXUjFiR1V4
                  name: Schedule1
                  type: businessHours
                  level: PEOPLE
                - id: Y2lzY29zcGFyazovL3VzL1VTRVJfU0NIRURVTEUvVkdWaGJTQkliMnhwWkdGNQ
                  name: Team Holiday
                  type: holidays
                  level: LOCATION
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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 User (and Location) Schedules
      operationId: getMySchedules
      description: 'Get Schedules for Call Settings for the authenticated user.


        Schedules are used to define specific time periods which can be applied to various Call Settings, such as Sequential Ring, or Priority Alert. These call settings perform the defined actions based on the time frame in the schedule, making it more convenient for users to manage their calls.


        This API requires a user auth token with a scope of `spark:telephony_config_read`.'
      tags:
      - Call Settings For Me With UserHub Phase2
      parameters: []
    post:
      summary: Add a User level Schedule for Call Settings
      operationId: createMySchedule
      description: 'Create a new Schedule for the authenticated user.


        Schedules are used to define specific time periods which can be applied to various Call Settings, such as Sequential Ring, or Priority Alert. These call settings perform the defined actions based on the time frame in the schedule, making it more convenient for users to manage their calls.


        This API requires a user auth token with a scope of `spark:telephony_config_write`.'
      tags:
      - Call Settings For Me With UserHub Phase2
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UserSchedulePostRequest'
            example:
              name: Holiday V2
              type: businessHours
              events:
              - name: Day_Shift
                startDate: '2020-03-18'
                endDate: '2020-03-18'
                startTime: 08:00
                endTime: '17:00'
                allDayEnabled: false
                recurrence:
                  recurForEver: true
                  recurEndDate: '2020-03-18'
                  recurEndOccurrence: 1
                  recurDaily:
                    recurInterval: 1
                  recurWeekly:
                    recurInterval: 1
                    sunday: false
                    monday: false
                    tuesday: false
                    wednesday: true
                    thursday: false
                    friday: false
                    saturday: false
      responses:
        '200':
          description: Schedule created successfully. Returns the Schedule ID.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseId'
              example:
                id: Y2lzY29zcGFyazovL3VzL1VTRVJfU0NIRURVTEUvU0c5c2FXUmhlU0JXTWc
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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.'
        '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.'
        '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.'
        '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).'
  /telephony/config/people/me/schedules/{scheduleType}/{scheduleId}:
    get:
      responses:
        '200':
          description: Schedule retrieved successfully for the authenticated user.
          headers: {}
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserScheduleGetResponse'
              example:
                id: Y2lzY29zcGFyazovL3VzL1VTRVJfU0NIRURVTEUvVTJOb1pXUjFiR1V4
                type: businessHours
                name: Schedule1
                events:
                - id: Y2lzY29zcGFyazovL3VzL1VTRVJfU0NIRURVTEVfRVZFTlQvUlZaRlRsUk9RVTFG
                  name: EVENT NAME
                  startDate: '2023-02-06'
                  endDate: '2023-02-06'
                  allDayEnabled: true
                  recurrence:
                    recurForEver: true
                    recurDaily:
                      recurInterval: 1
                - id: Y2lzY29zcGFyazovL3VzL1VTRVJfU0NIRURVTEVfRVZFTlQvUm5KcFpHRjVJREk9
                  name: Friday 2
                  startDate: '2020-10-30'
                  endDate: '2020-10-30'
                  startTime: '13:00'
                  endTime: '17:00'
                  allDayEnabled: false
                  recurrence:
                    recurForEver: true
                    recurWeekly:
                      sunday: false
                      monday: false
                      tuesday: false
                      wednesday: false
                      thursday: false
                      friday: true
                      saturday: false
        '400':
          description: 'Bad Request: The request was invalid or cannot be otherwise served.'
        '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 yo

# --- truncated at 32 KB (184 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/webex/refs/heads/main/openapi/webex-call-settings-for-me-with-userhub-phase2-api-openapi.yml