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

Webex Device Call Settings With Device Dynamic Settings API

The Device Call Settings With Device Dynamic Settings API from Webex — 9 operation(s) for device call settings with device dynamic settings.

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

The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 10 operations across 9 paths, and defines 36 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

10 operations 9 paths 36 schemas 5 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 3

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

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

Paths & Operations 10

Across 9 paths, the API surfaces 10 operations — 5 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Device Call Settings With Device Dynamic Settings 10
GET
/telephony/config/supportedDevices
Read the List of Supported Devices
readTheListOfSupportedDevices 3 params → 200400401403404405409410
GET
/telephony/config/devices/dynamicSettings/settingsGroups
Get Settings Groups
getSettingsGroups 3 params → 200400401403404405409410
POST
/telephony/config/lists/devices/dynamicSettings/actions/getSettings/invoke
Get Customer Device Dynamic Settings
getCustomerDeviceDynamicSettings 2 params body → 200400401403404405409410
POST
/telephony/config/lists/locations/{locationId}/devices/dynamicSettings/actions/getSettings/invoke
Get Location Device Dynamic Settings
getLocationDeviceDynamicSettings 3 params body → 200400401403404405409410
POST
/telephony/config/lists/devices/{deviceId}/dynamicSettings/actions/getSettings/invoke
Get Device Dynamic Settings
getDeviceDynamicSettings 2 params body → 200400401403404405409410
PUT
/telephony/config/devices/{deviceId}/dynamicSettings
Update Device Dynamic Settings
updateSpecifiedSettingsForTheDevice 2 params body → 204400401403404405409410
POST
/telephony/config/jobs/devices/dynamicDeviceSettings
Update Device Dynamic Settings Across Organization or Location
updatesDynamicDeviceSettingsAcrossOrganizationOrLocation 1 param body → 202400401403404405409410
GET
/telephony/config/jobs/devices/dynamicDeviceSettings
List Device Dynamic Settings Jobs
listDynamicDeviceSettingsJobs 3 params → 200400401403404405409410
GET
/telephony/config/jobs/devices/dynamicDeviceSettings/{jobId}
Get Device Dynamic Settings Job Status
getDeviceDynamicSettingsJobStatus 1 param → 200400401403404405409410
GET
/telephony/config/jobs/devices/dynamicDeviceSettings/{jobId}/errors
List Device Dynamic Settings Job Errors
listDynamicDeviceSettingsJobErrors 4 params → 200400401403404405409410

Schemas 36

The contract defines 36 schemas that model the data the API accepts and returns. The most detailed are PostDynamicDeviceSettingsJobResponse (14 properties), DeviceObject (9 properties), JobExecutionStatusObject (9 properties), stepExecutionStatusesObject (8 properties). Each schema is shown below with its type and property counts.

ItemObject
object
4 properties
LocationDevicePostResponseTag
object
5 properties
LocationParentLevel
string
The level from which the tag's parent value is inherited. If there is no parent level for this tag, this field will not be included in the response.
UpgradeChannelObject
string
DeviceDynamicSettingsSettingsGroupsGet
object
2 properties
DeviceObject
object
9 properties 7 required
DeviceSettingsGroup
object
5 properties
deviceOwner
object
4 properties 2 required
DeviceActivationStates
string
ACTIVATING - Indicates a device is activating. ACTIVATED - Indicates a device is activated. DEACTIVATED - Indicates a device is deactivated.
DevicePostResponseTag
object
5 properties 2 required
DeviceParentLevel
string
The level from which the tag's parent value is inherited. If there is no parent level for this tag, this field will not be included in the response.
MemberType
string
PEOPLE - Indicates the associated member is a person. PLACE - Indicates the associated member is a workspace.
DeviceDynamicSettingsListPostRequest
object
1 property
JobExecutionStatusObject
object
9 properties 5 required
PostDynamicDeviceSettingsJobResponse
object
14 properties 12 required
ErrorResponseObject
object
1 property
Action
string
ADD - Add action. DELETE - Delete action.
stepExecutionStatusesObject
object
8 properties 5 required
PostDynamicSettingsUpdateStartJobRequest
object
2 properties 1 required
DeviceSettingsGroupTag
object
1 property
LineType
string
PRIMARY - Primary line for the member. SHAREDCALLAPPEARANCE - Shared line for the member. A shared line allows users to receive and place calls to and from ano…
CustomerDeviceDynamicSettingsListPostRequest
object
1 property
LatestExecutionStatus
string
STARTING - Job has started. STARTED - Job is in progress. COMPLETED - Job has been completed. FAILED - Job has failed.
supportedDevicesObject
object
2 properties 2 required
LocationDeviceDynamicSettingsListPostResponse
object
3 properties
CustomerDeviceDynamicSettingsListPostResponse
object
3 properties
DynamicSettingsUpdateJobDevicePostItem
object
4 properties 3 required
CustomerDevicePostTag
object
5 properties
DeviceDynamicSettingsPutRequest
object
1 property
LocationDeviceDynamicSettingsListPostRequest
object
1 property
DeviceDynamicSettingsListPostResponse
object
2 properties 1 required
DynamicDeviceSettingsCustomerParentLevel
string
The level from which the tag's parent value is inherited. If there is no parent level for this tag, this field will not be included in the response.
ErrorMessageObject
object
3 properties
ErrorObject
object
2 properties
DevicePutItem
object
3 properties 2 required
DynamicDeviceSettingsJobListResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-device-call-settings-with-device-dynamic-settings-api-openapi.yml Raw ↑

Other APIs Webex publishes across the network.

Webex Address Book API
Webex Admin Audit Events API
Webex Agent Personal Greeting Files API
Webex Agent Summaries API
Webex Agent Wellbeing API
Webex Agents API
Webex AI Feature API
Webex API - Domain Management API
Webex Archive Users API
Webex Attachment Actions API
Webex Audio Files API
Webex Authorizations API
Where this information came from

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

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

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

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