Webex for Developers Changelog API

From September 8, 2025 [Get Shared-Line Appearance Members](/docs/api/v1/user-call-settings-2-2/get-shared-line-appearance-members) will be replaced with [Get Shared-Line Appearance Members New](/docs/api/v1/user-call-settings-2-2/get-shared-line-appearance-members-new) and [Search Shared-Line Appearance Members](/docs/api/v1/user-call-settings-2-2/search-shared-line-appearance-members) will be replaced by [Search Shared-Line Appearance Members New](/docs/api/v1/user-call-settings-2-2/search-shared-line-appearance-members-new) and [Put Shared-Line Appearance Members](/docs/api/v1/user-call-settings-2-2/put-shared-line-appearance-members) will be replaced by [Put Shared-Line Appearance Members New](/api/v1/user-call-settings-2-2/put-shared-line-appearance-members-new) and [Retrieve a person's Application Services Settings](/docs/api/v1/user-call-settings-1-2/retrieve-a-person-s-application-services-settings) will be replaced by [Retrieve a person's Application Services Settings New](/docs/api/v1/user-call-settings-2-2/retrieve-a-person-s-application-services-settings-new).

Mon, 28 Jul 2025 00:00:00 GMT

From September 8, 2025, Get Shared-Line Appearance Members will be replaced with Get Shared-Line Appearance Members New and Search Shared-Line Appearance Members will be replaced by Search Shared-Line Appearance Members New and Put Shared-Line Appearance Members will be replaced by Put Shared-Line Appearance Members New and Retrieve a person's Application Services Settings will be replaced by Retrieve a person's Application Services Settings New.

[Configure Caller ID Settings for a Person](/docs/api/v1/user-call-settings-1-2/configure-caller-id-settings-for-a-person), [Read Caller ID Settings for a Person](/docs/api/v1/user-call-settings-1-2/read-caller-id-settings-for-a-person),

Thu, 26 Jun 2025 00:00:00 GMT

Configure Caller ID Settings for a Person, Read Caller ID Settings for a Person, Configure Caller ID Settings for a Virtual Line, and Read Caller ID Settings for a Virtual Line will be impacted by the deprecation of the firstName and lastName fields for configuring caller ID and dialing names of users and virtual lines. Admins should now use directLineCallerIdName.selection and directLineCallerIdName.customName for configuring caller ID, and set dialing names with dialByFirstName and dialByLastName.

Configure Caller ID Settings for a Workspace and Read Caller ID Settings for a Workspace will see the deprecation of the displayName and displayDetail fields for configuring caller ID and dialing names of workspaces. Caller ID should now be configured with directLineCallerIdName.selection and directLineCallerIdName.customName, and dialing names with dialByName.

The following feature APIs will be impacted by the deprecation of the firstName and lastName fields for configuring caller ID and dialing names: Create an Auto Attendant, Get Details for an Auto Attendant, Update an Auto Attendant, Create a Call Queue with Customer Experience Essentials, Get Details for a Call Queue with Customer Experience Essentials, Update a Call Queue, Create a Hunt Group, Get Details for a Hunt Group, Update a Hunt Group, Create a new Paging Group, Get Details for a Paging Group, Update a Paging Group, Create a new Voicemail Group for a Location, Get Location Voicemail Group, Modify Location Voicemail Group, Get VoicePortal, and Update VoicePortal. Admins should now use directLineCallerIdName.selection and directLineCallerIdName.customName for configuring caller ID, and dialByName for configuring dialing names.

Create a Virtual Line, Read the List of Virtual Lines, and Update a Virtual Line will deprecate the callerIdFirstName and callerIdLastName fields for configuring virtual line caller ID. Instead, admins should use Configure Caller ID Settings for a Virtual Line and Read Caller ID Settings for a Virtual Line to configure and view virtual line caller ID settings.

These changes will take effect at the end of July 2025.

As an admin, you can now delete a recording using the [Delete a Recording By an Admin](/docs/api/v1/recordings/delete-a-recording-by-an-admin) API without specifying the `hostEmail` parameter as long as the recording to be deleted is on a site which is managed by the admin. The admin can delete a recording using this new API even if the "Allow hosts to reassign, edit, disable, and delete meeting" option is disabled on the target site.

Tue, 24 Jun 2025 00:00:00 GMT

As an admin, you can now delete a recording using the Delete a Recording By an Admin API without specifying the hostEmail parameter as long as the recording to be deleted is on a site which is managed by the admin. The admin can delete a recording using this new API even if the "Allow hosts to reassign, edit, disable, and delete meeting" option is disabled on the target site.

We have identified an issue with the guest-to-guest Service App in our developer program. When a Service App is deleted without first removing its authorizations, the license it consumes within your organization is not released and cannot be reused. To ensure proper license management, please make sure to remove all authorizations associated with the Service App before deleting it. This will free up the license for future use.

Thu, 12 Jun 2025 00:00:00 GMT

We have identified an issue with the guest-to-guest Service App in our developer program. When a Service App is deleted without first removing its authorizations, the license it consumes within your organization is not released and cannot be reused. To ensure proper license management, please make sure to remove all authorizations associated with the Service App before deleting it. This will free up the license for future use.

As an admin, you can now retrieve a meeting using a meeting ID with the [Get a Meeting By an Admin](/docs/api/v1/meetings/get-a-meeting-by-an-admin) API, or retrieve meetings with a meeting number or web link with the [List Meetings By an Admin](/docs/api/v1/meetings/list-meetings-by-an-admin) API. No `hostEmail` parameter or `password` is required, but sensitive attributes like `agenda`, `hostKey`, `password`, etc. are hidden from the response.

Mon, 09 Jun 2025 00:00:00 GMT

As an admin, you can now retrieve a meeting using a meeting ID with the Get a Meeting By an Admin API, or retrieve meetings with a meeting number or web link with the List Meetings By an Admin API. No hostEmail parameter or password is required, but sensitive attributes like agenda, hostKey, password, etc. are hidden from the response.

A new attribute `hasSlido` has been added to the response of the [Get a Meeting](/docs/api/v1/meetings/get-a-meeting) and [List Meetings](/docs/api/v1/meetings/list-meetings) APIs to indicate whether or not an ended meeting instance has Slido interactions. A new boolean filter `hasSlido` has been added to the [List Meetings](/docs/api/v1/meetings/list-meetings) API. If true, it only return meeting instances which have Slido interactions; if false, it only return those which have no Slido interactions; if it isn't specified, all meeting instances will be returned. Note that the `hasSlido` attribute is true for an ended meeting instance if Slido is enabled for the meeting and there are interactions like Q&A or polling in Slido.

Tue, 03 Jun 2025 00:00:00 GMT

A new attribute hasSlido has been added to the response of the Get a Meeting and List Meetings APIs to indicate whether or not an ended meeting instance has Slido interactions. A new boolean filter hasSlido has been added to the List Meetings API. If true, it only return meeting instances which have Slido interactions; if false, it only return those which have no Slido interactions; if it isn't specified, all meeting instances will be returned. Note that the hasSlido attribute is true for an ended meeting instance if Slido is enabled for the meeting and there are interactions like Q&A or polling in Slido.

As a meeting host, cohost or compliance officer, you can now end a meeting with a specified meeting ID using the [End a Meeting](/docs/api/v1/meetings/end-a-meeting) API.

Tue, 03 Jun 2025 00:00:00 GMT

As a meeting host, cohost or compliance officer, you can now end a meeting with a specified meeting ID using the End a Meeting API.

A new attribute `hasSlido` has been added to the response of the [Get a Meeting](/docs/api/v1/meetings/get-a-meeting) and [List Meetings](/docs/api/v1/meetings/list-meetings) APIs to indicate whether or not an ended meeting instance has Slido interactions. A new boolean filter `hasSlido` has been added to the [List Meetings](/docs/api/v1/meetings/list-meetings) API. If true, the APIs only return meeting instances which have Slido interactions; if false, they only return those which have no Slido interactions; if not specified, all meeting instances are returned. Note that the `hasSlido` attribute is true for an ended meeting instance if Slido is enabled for the meeting and there are interactions like Q&A or polling in Slido.

Fri, 30 May 2025 00:00:00 GMT

A new attribute hasSlido has been added to the response of the Get a Meeting and List Meetings APIs to indicate whether or not an ended meeting instance has Slido interactions. A new boolean filter hasSlido has been added to the List Meetings API. If true, the APIs only return meeting instances which have Slido interactions; if false, they only return those which have no Slido interactions; if not specified, all meeting instances are returned. Note that the hasSlido attribute is true for an ended meeting instance if Slido is enabled for the meeting and there are interactions like Q&A or polling in Slido.

Admins can now submit a request for up to 1,000 numbers in the `MOVE` operation type when using the [Initiate Number Jobs](/docs/api/v1/numbers/initiate-number-jobs) API. Additionally, the [Initiate Move Users Job](/docs/api/v1/user-call-settings-2-2/validate-or-initiate-move-users-job) has now been enhanced to support non-calling user moves.

Tue, 27 May 2025 00:00:00 GMT

Admins can now submit a request for up to 1,000 numbers in the MOVE operation type when using the Initiate Number Jobs API. Additionally, the Initiate Move Users Job has now been enhanced to support non-calling user moves.

Admins can now update the `ownerID` in a request when using [Reassign Recordings](/docs/api/v1/converged-recordings/reassign-recordings) to change the owner of a recording. This is particularly useful in cases involving virtual lines or workspaces that do not have an associated email address.

Thu, 15 May 2025 00:00:00 GMT

Admins can now update the ownerID in a request when using Reassign Recordings to change the owner of a recording. This is particularly useful in cases involving virtual lines or workspaces that do not have an associated email address.

In the near future, the `numberOfRings` parameter will be limited to values between 2 and 20 for User, Workspace, and Virtual Profile Call Forwarding and Voicemail `PUT` APIs. The same validation will also apply to `numberOfRings` and `baseLocationNumberOfRings` for the Workspace Sequential Ring API.

Mon, 12 May 2025 00:00:00 GMT

In the near future, the numberOfRings parameter will be limited to values between 2 and 20 for User, Workspace, and Virtual Profile Call Forwarding and Voicemail PUT APIs. The same validation will also apply to numberOfRings and baseLocationNumberOfRings for the Workspace Sequential Ring API.

The [Setup PSTN Connection for a Location](/docs/api/v1/pstn/setup-pstn-connection-for-a-location) API now requires the `spark-admin:telephony_pstn_read` scope in addition to the scope already documented.

Thu, 01 May 2025 00:00:00 GMT

The Setup PSTN Connection for a Location API now requires the spark-admin:telephony_pstn_read scope in addition to the scope already documented.

The new [Update a Virtual Extension](/docs/api/v1/beta-features-virtual-extensions/update-a-virtual-extension) and [Delete a Virtual Extension](/docs/api/v1/beta-features-virtual-extensions/delete-a-virtual-extension) APIs require the `Identity:contact` scope in addition to the roles and scopes already documented.

Tue, 29 Apr 2025 00:00:00 GMT

The new Update a Virtual Extension and Delete a Virtual Extension APIs require the Identity:contact scope in addition to the roles and scopes already documented.

When Cisco 8875 devices are upgraded to PhoneOS 3.4 or later, they will operate like desk phones. These devices can no longer be configured using [PUT settings](/docs/api/v1/device-call-settings/update-device-settings) and [GET settings API](/docs/api/v1/device-call-settings/get-device-settings). Instead, they should be configured in the same way as Cisco 9800 series devices, using the [Device Configuration APIs](/docs/api/v1/device-configurations). Additionally, these devices are no longer configurable at the location or organization level through the [Change Device Settings Job API](/docs/api/v1/device-call-settings/change-device-settings-across-organization-or-location-job).

Mon, 28 Apr 2025 00:00:00 GMT

When Cisco 8875 devices are upgraded to PhoneOS 3.4 or later, they will operate like desk phones. These devices can no longer be configured using PUT settings and GET settings API. Instead, they should be configured in the same way as Cisco 9800 series devices, using the Device Configuration APIs. Additionally, these devices are no longer configurable at the location or organization level through the Change Device Settings Job API.

Previously, authorized bots could access a person's pronouns based on Control Hub settings. However, to prioritize customer privacy and ensure data is used only when necessary, we are disabling this feature. This change should go into effect at the end of April, 2025.

Tue, 15 Apr 2025 00:00:00 GMT

Previously, authorized bots could access a person's pronouns based on Control Hub settings. However, to prioritize customer privacy and ensure data is used only when necessary, we are disabling this feature. This change should go into effect at the end of April, 2025.