Webex for Developers Changelog API

JWT token expiration in Integer format

Wed, 10 Sep 2025 00:00:00 GMT

Breaking: JWT token expiration in Integer format

We will follow a stricter implementation for the JWT guest token to follow the standards more closely. Previously a string was accepted in the exp field to indicate when the token expires. We are changing this field to allow an Integer only. This change will be enforced Nov 1, 2025. You can make the change right now as today both string and int will be accepted.

Example:

{..."exp":"1730793600",...}

{..."exp":1730793600, ...}

BYODS Alg Field

Wed, 10 Sep 2025 00:00:00 GMT

We have added a new field alg to the public key schema used in the Bring Your Own Device Service BYODS framework. This is an additive change that maintains backward compatibility.

Changes:

Added Field: alg - Algorithm identifier for the public key
Location: Public key objects within the BYODS framework
Type: String (expected values may include standard algorithm identifiers like "RS256", "ES256", etc.)

Stricter Header Validation - We've implemented stricter validation for API request headers

Mon, 08 Sep 2025 00:00:00 GMT

Notice: Stricter Header Validation

We've implemented stricter validation for API request headers. If your API calls suddenly stop working and you haven't made any changes on your end, please double-check your headers for correctness. Requests with incorrect or missing headers will now be rejected.

Examples: • If you send a GET request with any Content-Type header (e.g., Content-Type: application/json or Content-Type: application/x-www-form-urlencoded), the request may be rejected. • If you send a POST request with JSON or XML data but use Content-Type: application/x-www-form-urlencoded instead of the correct content type (e.g., application/json or application/xml), the request will also be rejected.

Configure Caller ID Settings for a Person - unicode caller ID in features

Mon, 25 Aug 2025 00:00:00 GMT

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.

If directLineCallerIdName.selection is set to DISPLAY_NAME, the caller ID value can be viewed and updated using the name field in the same APIs.

If a request includes any of the deprecated fields (firstName, lastName) and any of the new fields (directLineCallerIdName.selection, directLineCallerIdName.customName, or dialByName) as well, only the new fields will be processed and the deprecated fields will be ignored.

However, if only the deprecated fields are present, their combined value will be used for direct line caller ID and dialing configurations. If only one deprecated field is provided, the system will use the existing value of the missing field (if available) to calculate the combined value.

These changes will take effect by September 2025 and the deprecated fields (firstName, lastName) will be removed by the end of March 2026.

Configure Caller ID Settings for a Person - unicode caller ID in workspaces

Mon, 25 Aug 2025 00:00:00 GMT

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.

If directLineCallerIdName.selection is set to DISPLAY_NAME, admins can view and configure the corresponding caller ID value in the displayName field using the Get Workspace Details and Update a Workspace APIs.

If a request includes any of the deprecated fields (displayName, displayDetail) and any of the new fields (directLineCallerIdName.selection, directLineCallerIdName.customName, or dialByName) as well, only the new fields will be processed and the deprecated fields will be ignored.

These changes will take effect by September 2025 and the deprecated fields (displayName, displayDetail) will be removed by the end of March 2026.

Configure Caller ID Settings for a Person - unicode caller ID in users and virtual lines

Mon, 25 Aug 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 to configure caller ID, and dialByFirstName and dialByLastName to set dialing names.

If directLineCallerIdName.selection is set to DISPLAY_NAME, FIRSTNAME_LASTNAME, or LASTNAME_FIRSTNAME, admins can view the corresponding caller ID values in the firstName, lastName, and displayName fields using the Get Person Details and Get Details for a Virtual Line APIs for users and virtual lines, respectively. Admins can also update these fields and configure the caller ID for these selections, using the Update a Person and Update a Virtual Line APIs.

If a request includes any of the deprecated fields (firstName, lastName) and any of the new fields (directLineCallerIdName.selection, directLineCallerIdName.customName, dialByFirstName, or dialByLastName) as well, only the new fields will be processed and the deprecated fields will be ignored.

However, if only the deprecated fields are present, the corresponding dial-by field will be updated (dialByFirstName if firstName is present, or dialByLastName if lastName is present) and their combined value will be used for direct line caller ID configuration. If only one deprecated field is provided, the system will use the existing value of the missing field (if available) to calculate the combined value and configure the direct line caller ID.

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 by September 2025 and the deprecated fields (firstName, lastName) will be removed by the end of March 2026.

The Transfer Task API has been update to support entry point as a destination which allows users to transfer a task directly to an entry point in the organization.

Tue, 19 Aug 2025 00:00:00 GMT

The Transfer Task API has been update to support entry point as a destination which allows users to transfer a task directly to an entry point in the organization.

A new resource `scheduled-callback` has been added which allows an agent to schedule a callback request for a later date or time via the APIs.

Thu, 31 Jul 2025 00:00:00 GMT

A new resource scheduled-callback has been added which allows an agent to schedule a callback request for a later date or time via the APIs.

We are updating the rate limits on the People API to ensure fair access for all customers

Thu, 31 Jul 2025 00:00:00 GMT

We are updating the rate limits on the People API to ensure fair access for all customers. This change is being made because some accounts were making extremely frequent calls, impacting the experience for others. With the new limits, most customers will benefit from improved access. Some users may notice an increase in 429 (Too Many Requests) responses, though we are working to keep this to a minimum. Thank you for your understanding and support.

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.

In campaign manager APIs with the ability to configure preview specific parameters like offer timeout, auto-action and disabled actions, we've added support for two new preview modes: Preview Standard and Preview Direct. 2. We've added new preview task APIs to allow the agents to accept, skip, or remove contacts offered during a preview campaign.

Wed, 23 Jul 2025 00:00:00 GMT

In campaign manager APIs with the ability to configure preview specific parameters like offer timeout, auto-action and disabled actions:

Added support for two new preview modes: Preview Standard and Preview Direct.
Added new preview task APIs to allow the agents to accept, skip, or remove contacts offered during a preview campaign.

We are updating the artifact retention policy for the Serving API. Effective August 4, 2025, artifacts will be available for 24 hours (reduced from the previous 48 hours) before automatic deletion. This change aligns with security best practices and helps ensure the continued protection of your data. If you have any questions or need assistance adjusting your workflows, please contact our support team.

Tue, 15 Jul 2025 00:00:00 GMT

We are updating the artifact retention policy for the Serving API. Effective August 4, 2025, artifacts will be available for 24 hours (reduced from the previous 48 hours) before automatic deletion. This change aligns with security best practices and helps ensure the continued protection of your data. If you have any questions or need assistance adjusting your workflows, please contact our support team.

The Entry Point API has been updated with a new property for flow override settings. In addition, we've added the following new APIs - [Bulk partial update Contact Service Queue(s)](/webex-contact-center/docs/api/v1/contact-service-queues/bulk-partial-update-contact-service-queues), [Get specific User by ID](/webex-contact-center/docs/api/v1/users/get-specific-user-by-id). The following APIs have been deprecated - [List User Profile(s)](/webex-contact-center/docs/api/v1/user-profiles/list-user-profiles), [Update specific User Profile by ID](/webex-contact-center/docs/api/v1/user-profiles/update-specific-user-profile-by-id). Finally, the User Profile API `Create a new User Profile` has been removed. Enhanced user profile APIs with resource collection and access control lists are coming soon. Existing APIs still are functional until the new APIs are published and will become non-functional once the new APIs become available.

Wed, 25 Jun 2025 00:00:00 GMT

The Entry Point API has been updated with a new property for flow override settings. In addition, we've added the following new APIs - Bulk partial update Contact Service Queue(s), Get specific User by ID. The following APIs have been deprecated - List User Profile(s), Update specific User Profile by ID. Finally, the User Profile API Create a new User Profile has been removed. Enhanced user profile APIs with resource collection and access control lists are coming soon. Existing APIs still are functional until the new APIs are published and will become non-functional once the new APIs become available.

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.

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, 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.

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.

As part of the upcoming Queue Records (CLR) Search API GA, the following fields in the [taskLegDetails query](/webex-contact-center/docs/getting-started-with-search-api#query-definitions) of the [GraphQL Search API](/webex-contact-center/docs/api/v1/search/search) will be permanently removed after 15 June 2025. We previously issued deprecation notices for some of these changes in September and October 2024. If any of your `taskLegDetails` queries are using [fields from the list of removed fields, you must update your queries](https://assets.contentstack.io/v3/assets/bltd74e2c7e18c68b20/bltd87f1aa6620340e4/new-changelog-pdf-22.pdf) to ensure continued functionality of your API after the removal date. Failure to update will result in a validation error.

Mon, 19 May 2025 00:00:00 GMT

As part of the upcoming Queue Records (CLR) Search API GA, the following fields in the taskLegDetails query of the GraphQL Search API will be permanently removed after 15 June 2025. We previously issued deprecation notices for some of these changes in September and October 2024. If any of your taskLegDetails queries are using fields from the list of removed fields, you must update your queries to ensure continued functionality of your API after the removal date. Failure to update will result in a validation error.

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.

List and Publish APIs have been enabled for Flows. The [List Flows API](/documentation/flow/v1/list-flows-or-subflows) allows the customer to find all of its flows, and to perform some basic filtering to search for specific ones. [The Publish API](/documentation/flow/v1/publish-a-flow-or-subflow) allows a draft API to be moved to a published state. Together they enable transferring flows from one organization to another without having to manually retrieve the flow IDs and publish each one individually.

Sat, 12 Apr 2025 00:00:00 GMT

List and Publish APIs have been enabled for Flows. The List Flows API allows the customer to find all of its flows, and to perform some basic filtering to search for specific ones. The Publish API allows a draft API to be moved to a published state. Together they enable transferring flows from one organization to another without having to manually retrieve the flow IDs and publish each one individually.

Partner organizations that manage their customers through Webex Partner Hub can now download Partner Hub reports directly using the [Partner Reports Template](/docs/api/v1/partner-reports-templates) API.

Mon, 07 Apr 2025 00:00:00 GMT

Partner organizations that manage their customers through Webex Partner Hub can now download Partner Hub reports directly using the Partner Reports Template API.

For the convenience of users, the previous `List Meetings of a Meeting Series` API is merged into the [List Meetings](/docs/api/v1/meetings/list-meetings) API.

Fri, 04 Apr 2025 00:00:00 GMT

For user convenience, the previous List Meetings of a Meeting Series API has been merged into the List Meetings API.

guest-to-guest with e2e encryption

Mon, 31 Mar 2025 00:00:00 GMT

We are excited to announce a new feature: guest-to-guest meetings can now be set up with end-to-end encryption. To take advantage of this enhanced security, please ensure that the Service App for guest-to-guest meetings is reauthorized.

Video Duration Recalculation

Fri, 14 Mar 2025 00:00:00 GMT

The data for the Video Duration field in the Calling Media Quality report has occasionally been reported as higher than expected. We're addressing this discrepancy to make sure that the data accurately reflects the actual video duration during calls. This change will be applied to historical data, affecting records up to 13 months prior from when the change goes live and will be enacted starting 3/18. The Video Duration field also exists in the Calling Engagement report, but this change won't affect this report as it's being obsoleted.

Users will be now allowed to include IVR ports for a particular campaign. This field will be available while starting a new campaign using url: [create campaign request](/docs/api/v1/campaign-manager/create-campaign-request)

Thu, 06 Mar 2025 00:00:00 GMT

Users will be now allowed to include IVR ports for a particular campaign. This field will be available while starting a new campaign using url: create campaign request

As mentioned in the [November changelog](/docs/api/changelog#2024-november), the values of the `errorCodes` field returned by the [Get a Trunk](/docs/api/v1/call-routing/get-a-trunk) endpoint will be updated. This update is scheduled to take place in April 2025.

Mon, 03 Mar 2025 00:00:00 GMT

As mentioned in the November changelog, the values of the errorCodes field returned by the Get a Trunk endpoint will be updated. This update is scheduled to take place in April 2025.

We are excited to introduce a new group of APIs for [Domain Management](/docs/api/v1/domain-management). An administrator can [verify](/docs/api/v1/domain-management/verify-domain) a domain and [claim ownership](/docs/api/v1/domain-management/claim-domain) of it for their organization. Verifying a domain ensures that a user in a given organization belongs to that specific domain. Previously claimed domains can be released using the [unclaim](/docs/api/v1/domain-management/unclaim-domain) and [unverify](/docs/api/v1/domain-management/unverify-domain) APIs.

Mon, 24 Feb 2025 00:00:00 GMT

We are excited to introduce a new group of APIs for Domain Management. An administrator can verify a domain and claim ownership of it for their organization. Verifying a domain ensures that a user in a given organization belongs to that specific domain. Previously claimed domains can be released using the unclaim and unverify APIs.

HydrantId certificate for webexapis.com

Fri, 21 Feb 2025 00:00:00 GMT

Due to unforseen circumstances we have updated our internet SSL certificate issuer from GoDaddy to HydrantId. This change may require developers to update their applications to incorporate the new certificate chain. You can download the Identrust chain from here. Impact • Applications relying on the old certificate chain from GoDaddy may experience failures in establishing secure connections. • Developers need to update their applications to trust the new certificate chain issued by HydrantId. Action Required: • Review and update your application's SSL/TLS configuration to include the new certificate chain provided by HydrantId. • Test your applications to ensure compatibility with the new certificate chain and confirm that secure connections are established successfully.

As a meeting host, you can set up live streaming for a meeting with the `enabledLiveStream` and `liveStream` attributes when the meeting is created using [Create a Meeting](/docs/api/v1/meetings/create-a-meeting). When the meeting is started, the meeting host can start the live streaming by selecting the three dots, choosing Start live streaming and then Go live from the meeting client. The live streaming is started for the meeting without any ad-hoc configuration required. Live streaming can also be enabled for an existing meeting using [Patch a Meeting](/docs/api/v1/meetings/patch-a-meeting) or [Update a Meeting](/docs/api/v1/meetings/update-a-meeting) with the `enabledLiveStream` and `liveStream` attributes.

Fri, 14 Feb 2025 00:00:00 GMT

As a meeting host, you can set up live streaming for a meeting with the enabledLiveStream and liveStream attributes when the meeting is created using Create a Meeting. When the meeting is started, the meeting host can start the live streaming by selecting the three dots, choosing Start live streaming and then Go live from the meeting client. The live streaming is started for the meeting without any ad-hoc configuration required. Live streaming can also be enabled for an existing meeting using Patch a Meeting or Update a Meeting with the enabledLiveStream and liveStream attributes.

As a host or cohost of a meeting, you can invite a SIP participant to join the meeting via the [Call Out a SIP Participant](/docs/api/v1/meeting-participants-with-sip-callout/call-out-a-sip-participant) API. You can also cancel the call to a SIP participant before the ringing on the invited SIP device stops via the [Cancel Calling Out a SIP Participant](/docs/api/v1/meeting-participants-with-sip-callout/cancel-calling-out-a-sip-participant) API.

Tue, 11 Feb 2025 00:00:00 GMT

As a host or cohost of a meeting, you can invite a SIP participant to join the meeting via the Call Out a SIP Participant API. You can also cancel the call to a SIP participant before the ringing on the invited SIP device stops via the Cancel Calling Out a SIP Participant API.

Descriptions of the following fields have been added to [Get Detailed Call History](/docs/api/v1/reports-detailed-call-history/): Caller ID number, External caller ID number, Redirecting party UUID, Device owner UUID, Call Recording Platform Name, Call Recording Result, Call Recording Trigger, and Public Calling IP Address.

Thu, 06 Feb 2025 00:00:00 GMT

Descriptions of the following fields have been added to Get Detailed Call History: Caller ID number, External caller ID number, Redirecting party UUID, Device owner UUID, Call Recording Platform Name, Call Recording Result, Call Recording Trigger, and Public Calling IP Address.

The DECT serviceability password or the admin override password provide read/write access to DECT base stations for performing system serviceability and troubleshooting functions. New APIs have been added under [DECT Device Settings](/docs/api/v1/dect-devices-settings) to create and manage serviceability passwords.

Fri, 24 Jan 2025 00:00:00 GMT

The DECT serviceability password or the admin override password provide read/write access to DECT base stations for performing system serviceability and troubleshooting functions. New APIs have been added under DECT Device Settings to create and manage serviceability passwords.

Starting March 2nd, 2025, the `sharedLineIndex` field will be mandatory when `lineKeyType` is `SHARED_LINE` for the following APIs: [Modify Device Layout by Device ID](/docs/api/v1/device-call-settings/modify-device-layout-by-device-id), [Create a Line Key Template](/docs/api/v1/device-call-settings/create-a-line-key-template), and [Modify a Line Key Template] (/docs/api/v1/device-call-settings/modify-a-line-key-template).

Tue, 21 Jan 2025 00:00:00 GMT

Starting March 2nd, 2025, the sharedLineIndex field will be mandatory when lineKeyType is SHARED_LINE for the following APIs: Modify Device Layout by Device ID, Create a Line Key Template, and Modify a Line Key Template.

Main and breakout session alignment in WSMP

Tue, 21 Jan 2025 00:00:00 GMT

We are implementing an update to the API response structure for breakout sessions for meeting participants on the Webex Suite Meeting Platform (WSMP). This change is driven by the transition to our fully distributed, scalable, and resilient infrastructure.

Previous Behavior: In the past, when a participant moved from the main session to a breakout session, and then to another breakout session, the API response aligned the breakout sessions under a single main session: • MSession • BrO1 • BrO2

New Behavior: With WSMP, each breakout session will now appear under the main session every time, as follows: • MSession • BrO1 • MSession • BrO2

This adjustment means the API response will include the main session for each breakout session entry, even if only one main session exists. As a result, you will need to utilize session identifiers to consolidate these repeated main session entries in your reporting systems.

Please update your systems accordingly to accommodate this change.

As mentioned in the [November month's changelog](/docs/api/changelog#2024-november), the values of the `errorCodes` field returned by the [Get a Trunk](/docs/api/v1/call-routing/get-a-trunk) endpoint will be updated. This update is scheduled to take place in February 2025.

Tue, 21 Jan 2025 00:00:00 GMT

As mentioned in the November month's changelog, the values of the errorCodes field returned by the Get a Trunk endpoint will be updated. This update is scheduled to take place in February 2025.

new webhook signatures available

Mon, 13 Jan 2025 00:00:00 GMT

Webhooks for Webex events are provided with a X-Spark-Signature when a secret has been provided during webhook registration. The signature corresponds to the HMAC-SHA1 hash of the webhook payload. We now offer additional HMAC's namely HMAC-SHA256 and HMAC-SHA512. These can be found in the new header X-Webex-Signature.

The [List Contact Service Queue v3 API](/docs/api/v1/contact-service-queues/list-contact-service-queues) will be deprecated. Please use the [List Contact Service Queues v2 API](/docs/api/v1/contact-service-queues/list-contact-service-queues) instead.

Fri, 20 Dec 2024 00:00:00 GMT

The List Contact Service Queue v3 API will be deprecated. Please use the List Contact Service Queues v2 API instead.

ting January 27, 2025, the Emergency Call Back Number (ECBN)

Wed, 18 Dec 2024 00:00:00 GMT

Starting January 27, 2025, the Emergency Call Back Number (ECBN) setting retrieval and modification APIs will support using a Hunt Group and the previously supported types of People, Place, and Virtual Line. API callers should be prepared for the ECBN identifier and type associated with an entity to refer to a Hunt Group. Enhanced APIs will be Get Location ECBN Available Phone Numbers, Get Person ECBN Available Phone Numbers, Get Workspace ECBN Available Phone Numbers, Get Virtual Line ECBN Available Phone Numbers, Update a Location Emergency callback number, Update a Person's Emergency Callback Number, Update a Workspace Emergency Callback Number, Update a Virtual Line's Emergency Callback settings, Get a Location Emergency callback number, Get a Person's Emergency Callback Number, Get a Workspace Emergency Callback Number, Get the Virtual Line's Emergency Callback settings.

Scopes `cjp:user` or `cjp:config_write` will be required for authorization for performing CRUD operations for the [Campaign Manager APIs](/docs/api/v1/campaign-manager). Scope `cjp:user` will be required for authorization for the [Login](/docs/api/v1/agents/login), [Reload](/docs/api/v1/agents/reload) and [Create Task](/docs/api/v1/tasks-call-control/create-task) APIs.

Mon, 16 Dec 2024 00:00:00 GMT

Scopes cjp:user or cjp:config_write will be required for authorization for performing CRUD operations for the Campaign Manager APIs.

Scope cjp:user will be required for authorization for the Login, Reload and Create Task APIs.

New [Call Monitoring APIs](/docs/api/v1/call-monitoring) have been released to enable Contact Center Supervisors to monitor the quality of service being delivered across their multi-source contact centers.

Thu, 12 Dec 2024 00:00:00 GMT

New Call Monitoring APIs have been released to enable Contact Center Supervisors to monitor the quality of service being delivered across their multi-source contact centers.

Error code change

Thu, 21 Nov 2024 00:00:00 GMT

The values of the errorCodes field returned by the Get a Trunk endpoint will be changing on January 24, 2025. Please prepare your code to use these new values:

Old Error Code	New Error Code
`E1001`	`F_TO_FQDN_DNS_FAILURE`
`E1002`	`F_TO_CONN_TRANSPORT_ISSUE`
`E1003`	`F_TO_CONN_CERT_INVALID_CA`
`E1004`	`F_TO_CONN_CERT_EXPIRED`
`E1005`	`F_TO_CONN_CERT_EXPIRED_CA`
`E1006`	`F_TO_FQDN_FQDN_MISSING_CN_SAN`
`E1007`	`E_TO_NO_RESPONSE`
`E1008`	`F_FROM_CONN_CERT_INVALID_CERT`
`E1009`	`F_FROM_CONN_CERT_DISTRUST_CA`
`E1010`	`F_FROM_CONN_CERT_EXPIRED_CERT_CHAIN`
`E1011`	`F_FROM_FAILED_SIP_OPTIONS`
`E1012`	`E_FROM_SERVER_ERROR_UNAVAILABLE`
`E1013`	`F_TO_CONN_CERT_REVOKED_CERT`
`E1014`	`F_FROM_CONN_CERT_REVOKED_CERT`
`E1015`	`F_FROM_CONN_CERT_EXPIRED`
`E1016`	`F_FROM_CONN_CERT_ERROR`
`E1017`	`F_TO_CONN_CERT_ERROR`

Starting on January 16, 2025, the functions `Desktop.actions.getWrapUpCodes()` and `Desktop.actions.getIdleCodes()` will be deprecated and replaced by a paginated version of the function to fetch AUX codes. The new function, `Desktop.agentConfigJsApi.fetchPaginatedAuxCodes(\{workType, page, pageSize, search, customFilter})`, will handle the fetching of AUX codes. The `workType` parameter should be set to either `WRAP_UP_CODE` or `IDLE_CODE` to specify the type of AUX code that needs to be retrieved. This transition is part of an effort to improve the efficiency and functionality of AUX code retrieval within the system.

Thu, 14 Nov 2024 00:00:00 GMT

Starting on January 16, 2025, the functions Desktop.actions.getWrapUpCodes() and Desktop.actions.getIdleCodes() will be deprecated and replaced by a paginated version of the function to fetch AUX codes. The new function, Desktop.agentConfigJsApi.fetchPaginatedAuxCodes(\{workType, page, pageSize, search, customFilter}), will handle the fetching of AUX codes. The workType parameter should be set to either WRAP_UP_CODE or IDLE_CODE to specify the type of AUX code that needs to be retrieved. This transition is part of an effort to improve the efficiency and functionality of AUX code retrieval within the system.

Starting from May 16, 2025, the JavaScript SDK will be updated to a major version where the old methods will be deprecated and replaced by their newer v2 versions. Although the functionalities will remain the same, developers need to transition to using the updated methods: `acceptV2`, `endV2()`, `cancelTaskV2()`, `pauseRecordingV2()`, `resumeRecordingV2()`, `wrapupV2()`, `consultV2()`, `consultEndV2()`, `consultConferenceV2()`, `exitConference()`, `consultTransferV2()`, `blindTransferV2()`, `vTeamTransferV2()`, and `buddyAgentsV2()`. This change is necessary to ensure compatibility and leverage the improvements made in the newer versions of these methods.

Thu, 14 Nov 2024 00:00:00 GMT

Starting from May 16, 2025, the JavaScript SDK will be updated to a major version where the old methods will be deprecated and replaced by their newer v2 versions. Although the functionalities will remain the same, developers need to transition to using the updated methods: acceptV2, endV2(), cancelTaskV2(), pauseRecordingV2(), resumeRecordingV2(), wrapupV2(), consultV2(), consultEndV2(), consultConferenceV2(), exitConference(), consultTransferV2(), blindTransferV2(), vTeamTransferV2(), and buddyAgentsV2(). This change is necessary to ensure compatibility and leverage the improvements made in the newer versions of these methods.

Deprecation of the rooms/meetingInfo

Tue, 12 Nov 2024 00:00:00 GMT

As highlighted in the API Behavior Changes document, the rooms/meetingInfo API may not return information after an organization was moved to the Webex Suite Meetings Platform. As explained, the reason is that in WSMP, there is only a loose concept of a space meeting. The meeting does not happen in the space but must be scheduled via the /meetings REST endpoints. The meetings REST endpoint also provides the SIP dial info for the meeting like in this example response. Please utilize this REST endpoint to avoid service disruption.

   ...
    "siteUrl": "site4-example.webex.com",
    "webLink": "https://site4-example.webex.com/site4/j.php?MTID=md41817da6a55b0925530cb88b3577b1e",
    "registerLink": "https://cisco.webex.com/weblink/register/r55981368ee48e2a6f00b93231508c404",
    "sipAddress": "123456789@site4-example.webex.com",
    ...

The /meetingInfo endpoint is now deprecated, and we may shut it down entirely on January 31, 2025, when most customers should be on WSMP.

Location changes in Meeting Attendee Report

Mon, 11 Nov 2024 00:00:00 GMT

Meeting Attendee Report Update We're updating the Meeting Attendee report to accurately reflect the values for LOCATION field. We'll be labeling the LOCATION column as LOCATION (DEPRECATED) and adding new COUNTRY, STATE, and CITY columns for more specific location data. Additionally, the OS and BROWSER columns will now include version information.

As a reminder, effective today, the field `answerConfirmationEnabled` has been renamed to `answerConfirmationRequiredEnabled` within the simultaneous ring settings of the Workspace API. This change applies to both the [GET](/docs/api/v1/workspace-call-settings/retrieve-simultaneous-ring-settings-for-a-workspace) and [MODIFY](/docs/api/v1/workspace-call-settings/modify-simultaneous-ring-settings-for-a-workspace) endpoints. During the transition period ( [original change log published on 30th August 2024](/docs/api/changelog#2024-august) ), both fields were accessible in the payload for `GET` and `MODIFY` operations. Please ensure that your implementations have been updated to reflect this change.

Thu, 17 Oct 2024 00:00:00 GMT

As a reminder, effective today, the field answerConfirmationEnabled has been renamed to answerConfirmationRequiredEnabled within the simultaneous ring settings of the Workspace API. This change applies to both the GET and MODIFY endpoints. During the transition period ( original change log published on 30th August 2024 ), both fields were accessible in the payload for GET and MODIFY operations. Please ensure that your implementations have been updated to reflect this change.

The following fields in the [```taskLegDetails```]( /docs/getting-started-with-search-api) query of [GraphQL Search API ](/docs/api/v1/search/search) are now marked as deprecated: The following fields in the taskLegDetails query of GraphQL Search API are now marked as deprecated: 1. isBarged 2. isContactOffered 3. contactReason 4. botName 5. isMonitored 6. totalMonitoringCount 7. silentMonitoringCount 8. fullMonitoringCount 9. midcallMonitoringCount 10. resumedCount 11. overflowCount 12. pausedDuration 13. pausedCount 14. isChildLeg These fields are still available for use but will be removed from the API response after December 2024.

Tue, 15 Oct 2024 00:00:00 GMT

The following fields in the taskLegDetails query of GraphQL Search API are now marked as deprecated:

The following fields in the taskLegDetails query of GraphQL Search API are now marked as deprecated:

isBarged
isContactOffered
contactReason
botName
isMonitored
totalMonitoringCount
silentMonitoringCount
fullMonitoringCount
midcallMonitoringCount
resumedCount
overflowCount
pausedDuration
pausedCount
isChildLeg

These fields are still available for use but will be removed from the API response after December 2024.

Guest Issuer EOL

Fri, 11 Oct 2024 00:00:00 GMT

The Guest Issuer API function will reach its End of Life (EOL) on December 31, 2025. After this date, the Guest Issuer approach will no longer be supported or available.
All guest issuer apps must transition to using Service Apps for creating temporary identities to ensure continuity and take advantage of the enhanced features and support offered by Service Apps.

- [Consult Transfer Task API](/docs/api/v1/tasks-call-control/consult-transfer-task) will not work during a conference call If the multiparty conference feature is enabled for the tenant. Instead, the consulting Agent can exit the conference using [Exit Conference Task API](/docs/api/v1/tasks-call-control/exit-conference-task) - [Consult End Task API](/docs/api/v1/tasks-call-control/consult-end-task) will not work to end the conference call if multiparty conference feature is enabled for the tenant. Instead, [End Task API](/docs/api/v1/tasks-call-control/end-task) can be used to end the entire call.

Wed, 02 Oct 2024 00:00:00 GMT

Consult Transfer Task API will not work during a conference call If the multiparty conference feature is enabled for the tenant. Instead, the consulting Agent can exit the conference using Exit Conference Task API
Consult End Task API will not work to end the conference call if multiparty conference feature is enabled for the tenant. Instead, End Task API can be used to end the entire call.

The Secure Global Variable feature referenced [here](https://help.webex.com/en-us/article/nv7abhz/What's-new-for-administrators-in-Webex-Contact-Center#topic_D8159C942D4EE10D3C86F7C043C86722) will be enabled for all the tenants by November 30, 2024. To ensure the continued confidentiality of your sensitive data, please follow the steps outlined in the[ attached PDF](https://s3.amazonaws.com/devportal.cms.intgus1/SGV_1_d75bc3f9fa.pdf).

Mon, 30 Sep 2024 00:00:00 GMT

The Secure Global Variable feature referenced here will be enabled for all the tenants by November 30, 2024. To ensure the continued confidentiality of your sensitive data, please follow the steps outlined in the attached PDF.

The ```callbackOrigin``` field in the [Create Tasks API](/docs/api/v1/tasks-call-control/create-task) has been updated to reflect that ```web``` is the only supported value.

Fri, 27 Sep 2024 00:00:00 GMT

The callbackOrigin field in the Create Tasks API has been updated to reflect that web is the only supported value.

Update the Organization Name

Wed, 25 Sep 2024 00:00:00 GMT

We are excited to announce the release of a new API that enables administrators to manage organizational details more efficiently. Key Features include: • Get Organization Details: Administrators can now retrieve comprehensive details about their organization, including current name, status, and other pertinent information. • Update Organization Name: This new functionality allows administrators to easily update the organization's name through a simple API call.

For detailed information, please refer to our API reference.

The following fields in the [taskLegDetails query](/docs/getting-started-with-search-api#query-definitions) of [GraphQL Search API](/docs/api/v1/search/search) are now marked as deprecated: - ```monitorFullName``` - ```bargedInDuration``` - ```bargedInCount``` - ```bargedInFailedCount``` These fields are still available for use but will be removed from the API response after December 2024.

Wed, 25 Sep 2024 00:00:00 GMT

The following fields in the taskLegDetails query of GraphQL Search API are now marked as deprecated:

monitorFullName
bargedInDuration
bargedInCount
bargedInFailedCount

These fields are still available for use but will be removed from the API response after December 2024.

The wrapup method of the ```agentContact``` module has been updated with validation for ```auxCodeId``` field. This field has to be a valid Id corresponding to the Wrap-up code configured in Control Hub. Zero is no longer a valid value and will not be supported. Wrap-up codes indicate the result of customer contacts, such as successful resolution or escalation of the contact. Creating and managing auxiliary codes requires an administrator role and the appropriate ```cjp:config_write``` or ```cjp:config_read``` scopes, maximum length 36 characters. WrapUp code should be from the list of codes configured for an Agent at the Desktop Profile Configuration in Control Hub.- Beginning October 29, 2024, the ```wrapup()``` method will no longer accept invalid wrapup code.- Please find a Vidcast explaining the above change [here](https://app.vidcast.io/share/613379a1-2c5d-4d7a-b072-13132008be43).

Tue, 17 Sep 2024 00:00:00 GMT

The wrapup method of the agentContact module has been updated with validation for auxCodeId field. This field has to be a valid Id corresponding to the Wrap-up code configured in Control Hub. Zero is no longer a valid value and will not be supported. Wrap-up codes indicate the result of customer contacts, such as successful resolution or escalation of the contact. Creating and managing auxiliary codes requires an administrator role and the appropriate cjp:config_write or cjp:config_read scopes, maximum length 36 characters. WrapUp code should be from the list of codes configured for an Agent at the Desktop Profile Configuration in Control Hub.

Beginning October 29, 2024, the wrapup() method will no longer accept invalid wrapup code.
Please find a Vidcast explaining the above change here.

SDK EOL and upgrade path

Thu, 12 Sep 2024 00:00:00 GMT

We'd like to formally announce the SDK version v2 will reach its end-of-life (EOL) on September 30, 2025. The v1 SDKs are already EOL. As indicated on this change log in March and May we strongly encourage all users to migrate to SDK v3 (latest version: webex@3.4.0) at your earliest convenience to continue getting SDK support and feature upgrades while avoiding service disruptions on the Webex Suite Meetings Platform. Please refer to our Migration Guide for detailed instructions on making the transition.

A new version of the [List Skill API](/docs/api/v1/skill/list-skill) has been added.

Sun, 08 Sep 2024 00:00:00 GMT

A new version of the List Skill API has been added.

A new version of the [List Team API](/docs/api/v1/team/list-teams) has been added.

Sun, 08 Sep 2024 00:00:00 GMT

A new version of the List Team API has been added.

A new version of the [Create a Team API](/docs/api/v1/team/create-a-team) has been added.

Sun, 08 Sep 2024 00:00:00 GMT

A new version of the Create a Team API has been added.

A new API has been added to the [Outdial ANI](/docs/api/v1/outdial-ani) resource, [List Outdial ANI entries](/docs/api/v1/outdial-ani/list-outdial-ani-entries)

Sun, 08 Sep 2024 00:00:00 GMT

A new API has been added to the Outdial ANI resource, List Outdial ANI entries

A new version of [List Contact Service Queue](/docs/api/v1/contact-service-queues/list-contact-service-queues) has been added.

Sun, 08 Sep 2024 00:00:00 GMT

A new version of List Contact Service Queue has been added.

A new version of the [List Entry Points API](/docs/api/v1/entry-point/list-entry-points) has been added.

Sun, 08 Sep 2024 00:00:00 GMT

A new version of the List Entry Points API has been added.

Versions 2 and 3 of the Get All configuration APIs have been updated to support projection and filtration. This enhancement applies to most of the relevant fields. For more details, you can refer to the documentation for each individual Get All API where you will find a list of mentioned fields that are not applicable. The Configuration APIs include the following resources: Address Book, Audio Files, Auxiliary Code, Desktop Layout, Desktop Profile, Dial Plan, Dial Number, Entry Point, Global Variables, Multimedia Profile, Outdial ANI, Contact Service Queue, Site, Team, Skill Profile, Skill, User Profiles, Users, Work Types, Contact Number, Business Hour, Holiday List, and Overrides.

Sun, 08 Sep 2024 00:00:00 GMT

Versions 2 and 3 of the Get All configuration APIs have been updated to support projection and filtration. This enhancement applies to most of the relevant fields. For more details, you can refer to the documentation for each individual Get All API where you will find a list of mentioned fields that are not applicable.

The Configuration APIs include the following resources: Address Book, Audio Files, Auxiliary Code, Desktop Layout, Desktop Profile, Dial Plan, Dial Number, Entry Point, Global Variables, Multimedia Profile, Outdial ANI, Contact Service Queue, Site, Team, Skill Profile, Skill, User Profiles, Users, Work Types, Contact Number, Business Hour, Holiday List, and Overrides.

A new [User Profiles](/docs/api/v1/user-profiles) app module ```Agent Wellbeing(m_agent_wellbeing)``` has been added in the [User Profiles](/docs/api/v1/user-profiles) entity to manage access control for Agent wellbeing configuration features.

Fri, 06 Sep 2024 00:00:00 GMT

A new User Profiles app module Agent Wellbeing(m_agent_wellbeing) has been added in the User Profiles entity to manage access control for Agent wellbeing configuration features.

New [Users APIs](/docs/api/v1/users) have been added. - [List incoming reference entities by ID for User Profiles ](/docs/api/v1/user-profiles/get-user-profile-by-id) - [Bulk export Users](/docs/api/v1/users/bulk-export-users)

Fri, 06 Sep 2024 00:00:00 GMT

New Users APIs have been added.

List incoming reference entities by ID for User Profiles
Bulk export Users

New [Auxiliary Code APIs](/docs/api/v1/auxiliary-code) have been added. - [List incoming reference entities by ID for Auxiliary Code](/docs/api/v1/auxiliary-code/list-incoming-reference-entities-by-id-for-auxiliary-code) - [Bulk save Auxiliary Codes](/docs/api/v1/auxiliary-code/bulk-save-auxiliary-codes) - [Bulk partial update Auxiliary Codes](/docs/api/v1/auxiliary-code/bulk-partial-update-auxiliary-codes) - [Purge Inactive Auxiliary Codes](/docs/api/v1/auxiliary-code/purge-inactive-auxiliary-codes)

Fri, 06 Sep 2024 00:00:00 GMT

New Auxiliary Code APIs have been added.

List incoming reference entities by ID for Auxiliary Code
Bulk save Auxiliary Codes
Bulk partial update Auxiliary Codes
Purge Inactive Auxiliary Codes

For consistency with other APIs, we will be renaming the field `answerConfirmationEnabled` to `answerConfirmationRequiredEnabled` within the simultaneous ring settings for the Workspace API. This modification affects the [GET](/docs/api/v1/workspace-call-settings/retrieve-simultaneous-ring-settings-for-a-workspace) and [UPDATE](/docs/api/v1/workspace-call-settings/modify-simultaneous-ring-settings-for-a-workspace) endpoints. The change will take effect on October 4, 2024.

Fri, 30 Aug 2024 00:00:00 GMT

For consistency with other APIs, we will be renaming the field answerConfirmationEnabled to answerConfirmationRequiredEnabled within the simultaneous ring settings for the Workspace API. This modification affects the GET and UPDATE endpoints. The change will take effect on October 11, 2024. Throughout the transition period, both fields will be accessible in the payload for GET and MODIFY operations.

guest-to-guest meeting availability

Mon, 26 Aug 2024 00:00:00 GMT

Guest-to-Guest (G2G) meetings are now available, allowing non-licensed users to conduct fully featured meetings on the Webex Suite Meetings Platform (WSMP). These G2G meetings replace space-backend meetings, which are incompatible with WSMP. The new G2G feature is supported by a new license and order-SKU that covers the number of simultaneous meetings rather than individual users. For more details, please refer to the guide.

As an administrator, you can reassign a list of call recordings or all call recordings of a particular user to a new user through the [Reassign Recording](docs/api/v1/converged-recordings/reassign-recordings/) endpoint.

Fri, 23 Aug 2024 00:00:00 GMT

As an administrator, you can reassign a list of call recordings or all call recordings of a particular user to a new user through the Reassign Recording endpoint.

Service numbers are now supported for Premises-based PSTN. These are local telephone numbers considered as high utilization or concurrent, making them ideal for assignment to high-volume services such as Auto Attendants, Hunt Groups, and Call Queues. The [Add Numbers](/docs/api/v1/numbers/add-phone-numbers-to-a-location), [Get Numbers](/docs/api/v1/numbers/get-phone-numbers-for-an-organization-with-given-criterias), and [Initiate Number Jobs](/docs/api/v1/numbers/initiate-number-jobs) APIs are modified to support service numbers. Additionally, feature-specific available numbers APIs such as [Hunt Group](/docs/api/v1/features-hunt-group/get-hunt-group-primary-available-phone-numbers), [Location](/docs/api/v1/location-call-settings/get-location-call-intercept-available-phone-numbers), [Person](/docs/api/v1/user-call-settings/get-person-primary-available-phone-numbers), and [Workspace](/docs/api/v1/workspace-call-settings/get-workspace-fax-message-available-phone-numbers) have been added to help identify numbers that can be associated with specific members or features. These feature-specific APIs are streamlined with fewer parameters, making them more easily to use as alternatives to the more general [Get Numbers](/docs/api/v1/numbers/get-phone-numbers-for-an-organization-with-given-criterias) API.

Wed, 21 Aug 2024 00:00:00 GMT

Service numbers are now supported for Premises-based PSTN. These are local telephone numbers considered as high utilization or concurrent, making them ideal for assignment to high-volume services such as Auto Attendants, Hunt Groups, and Call Queues. The Add Numbers, Get Numbers, and Initiate Number Jobs APIs are modified to support service numbers. Additionally, feature-specific available numbers APIs such as Hunt Group, Location, Person, and Workspace have been added to help identify numbers that can be associated with specific members or features. These feature-specific APIs are streamlined with fewer parameters, making them more easily to use as alternatives to the more general Get Numbers API.

A new webhook resource allows you to receive notifications for status changes of admin batch jobs, reducing the need for manual status checks. For setup instructions and more details, see [Webhooks Reference Page](/docs/api/v1/webhooks).

Wed, 21 Aug 2024 00:00:00 GMT

A new webhook resource allows you to receive notifications for status changes of admin batch jobs, reducing the need for manual status checks. For setup instructions and more details, see Webhooks Reference Page.

The [Consult Task API](/docs/api/v1/tasks-call-control/consult-task) has been updated by adding a new parameter ```holdParticipants``` to the request body. The ```destinationType``` parameter in the request body for the [Consult Conference API](/docs/api/v1/tasks-call-control/consult-conference-task) and [Consult Transfer API](/docs/api/v1/tasks-call-control/consult-transfer-task) has been updated to support ```entryPoint```.

Tue, 20 Aug 2024 00:00:00 GMT

The Consult Task API has been updated by adding a new parameter holdParticipants to the request body.

The destinationType parameter in the request body for the Consult Conference API and Consult Transfer API has been updated to support entryPoint.

A new [Exit Conference Task API](/docs/api/v1/tasks-call-control/exit-conference-task) has been added.

Tue, 20 Aug 2024 00:00:00 GMT

A new Exit Conference Task API has been added.

As a meeting host, you can [Create a Meeting](/docs/api/v1/meetings/create-a-meeting), [Patch a Meeting](/docs/api/v1/meetings/patch-a-meeting), or [Update a Meeting](/docs/api/v1/meetings/update-a-meeting) with watermark settings by specifying the `enabledAudioWatermark`, `enabledVisualWatermark`, and `visualWatermarkOpacity` attributes. These attributes can also be returned when you [Get a Meeting](/docs/api/v1/meetings/get-a-meeting), [List Meetings](/docs/api/v1/meetings/list-meetings), or [List Meetings of a Meeting Series](/docs/api/v1/meetings/list-meetings-of-a-meeting-series).

Mon, 19 Aug 2024 00:00:00 GMT

As a meeting host, you can Create a Meeting, Patch a Meeting, or Update a Meeting with watermark settings by specifying the enabledAudioWatermark, enabledVisualWatermark, and visualWatermarkOpacity attributes. These attributes can also be returned when you Get a Meeting, List Meetings, or List Meetings of a Meeting Series.

New attributes `hasRegistration`, `hasRegistrants`, and `hasPostEventSurvey` are returned in the [Get a Meeting](/docs/api/v1/meetings/get-a-meeting), [List Meetings](/docs/api/v1/meetings/list-meetings), and [List Meetings of a Meeting Series](/docs/api/v1/meetings/list-meetings-of-a-meeting-series) APIs. The `hasRegistration` and `hasRegistrants` attributes only apply to ended meetings or webinar instances, while the `hasPostEventSurvey` attribute only applies to ended webinar instances.

Mon, 19 Aug 2024 00:00:00 GMT

New attributes hasRegistration, hasRegistrants, and hasPostEventSurvey are returned in the Get a Meeting, List Meetings, and List Meetings of a Meeting Series APIs. The hasRegistration and hasRegistrants attributes only apply to ended meetings or webinar instances, while the hasPostEventSurvey attribute only applies to ended webinar instances.

New Webex Meeting Widget version 1.27.0

Wed, 14 Aug 2024 00:00:00 GMT

The Webex Meeting Widget 1.27.0 is now available. This widget allows you to seamlessly integrate essential Webex functionality into your website, eliminating the need to build an app from scratch using the SDK. New Features: • Support for Node.js 20 • Compatibility with React 18.3.1 To get started, simply include the widget in your NPM applications from @webex/widgets. For more detailed information about Webex widgets, please visit our documentation.

We have updated the base URLs for the [CJDS APIs](/docs/api/v1/journey-admin) across several environments: | Region | URL | | -------------- | :-----------------------------: | | US | https://api.wxcc-us1.cisco.com | | EU 1 | https://api.wxcc-eu1.cisco.com | | EU 2 | https://api.wxcc-eu2.cisco.com | If you are using any previous URLs, please re-enable the Webex Contact Center connector as outlined on the [Getting Started page](/docs/journey-getting-started) to ensure you continue receiving contact center events for the journey widget.

Wed, 14 Aug 2024 00:00:00 GMT

We have updated the base URLs for the CJDS APIs across several environments:

Region	URL
US	https://api.wxcc-us1.cisco.com
EU 1	https://api.wxcc-eu1.cisco.com
EU 2	https://api.wxcc-eu2.cisco.com

If you are using any previous URLs, please re-enable the Webex Contact Center connector as outlined on the Getting Started page to ensure you continue receiving contact center events for the journey widget.

Effective February 13, 2025, updating the PSTN connection type and ID for a location will no longer be supported via the [Update Location Webex Calling Details](/docs/api/v1/location-call-settings/update-location-webex-calling-details) API. Instead, this functionality will be supported through the [Setup PSTN Connection for a Location](/docs/api/v1/pstn/setup-pstn-connection-for-a-location) API.

Tue, 13 Aug 2024 00:00:00 GMT

Effective February 13, 2025, updating the PSTN connection type and ID for a location will no longer be supported via the Update Location Webex Calling Details API. Instead, this functionality will be supported through the Setup PSTN Connection for a Location API.

The `wrapup` method of the [agentContact module ](/docs/desktop) has been updated with validation for `auxCodeId` field. This field has to be a valid Id corresponding to the Wrap-up code configured in Control Hub. Zero is no longer a valid value and will not be supported. Wrap-up codes indicate the result of customer contacts, such as successful resolution or escalation of the contact. Creating and managing auxiliary codes requires an administrator role and the appropriate `cjp:config_write` or `cjp:config_read` scopes, maximum length 36 characters.

Wed, 07 Aug 2024 00:00:00 GMT

The wrapup method of the agentContact module has been updated with validation for auxCodeId field. This field has to be a valid Id corresponding to the Wrap-up code configured in Control Hub. Zero is no longer a valid value and will not be supported. Wrap-up codes indicate the result of customer contacts, such as successful resolution or escalation of the contact. Creating and managing auxiliary codes requires an administrator role and the appropriate cjp:config_write or cjp:config_read scopes, maximum length 36 characters.

Separate destinations can now be configured for routing calls when the hunt group is busy or all agents are unreachable. To support this, new fields `busyRedirect` and `businessContinuityRedirect` have been added to the [CREATE](/docs/api/v1/features-hunt-group/create-a-hunt-group), [UPDATE](/docs/api/v1/features-hunt-group/update-a-hunt-group), and [GET Hunt Group](/docs/api/v1/features-hunt-group/get-details-for-a-hunt-group) endpoints. Starting September 16, 2024, support for the `businessContinuity` object will be removed from the request and response payloads of these endpoints.

Fri, 02 Aug 2024 00:00:00 GMT

Separate destinations can now be configured for routing calls when the hunt group is busy or all agents are unreachable. To support this, new fields busyRedirect and businessContinuityRedirect have been added to the CREATE, UPDATE, and GET Hunt Group endpoints. Starting September 16, 2024, support for the businessContinuity object will be removed from the request and response payloads of these endpoints.

Wholesale partners now include `locationId` in the user-level reconciliation reports of [Wholesale Billing Reports](docs/api/v1/wholesale-billing). Customer-level reconciliation reports with `locationId` will be available soon.

Thu, 01 Aug 2024 00:00:00 GMT

Wholesale partners can now see the locationId column in the USER level reconciliation reports of Wholesale Billing Reports. CUSTOMER level reconciliation reports with locationId will be available by September 1st, 2024.

Users can obtain scheduling permissions via the [Get Scheduling Options](/docs/api/v1/meeting-preferences/get-scheduling-options) API and update them using the [Update Scheduling Options](/docs/api/v1/meeting-preferences/update-scheduling-options) API with the `delegateEmails` parameter. Additionally, users can add new delegate emails with the [Insert Delegate Emails](/docs/api/v1/meeting-preferences/insert-delegate-emails) API and remove existing ones with the [Delete Delegate Emails](/docs/api/v1/meeting-preferences/delete-delegate-emails) API.

Fri, 19 Jul 2024 00:00:00 GMT

Users can obtain scheduling permissions via the Get Scheduling Options API and update them using the Update Scheduling Options API with the delegateEmails parameter. Additionally, users can add new delegate emails with the Insert Delegate Emails API and remove existing ones with the Delete Delegate Emails API.

The scopes `cjp-analyzer:config_read` and `cjp-analyzer:read` are supported by some APIs, however since these scopes cannot be provisioned for integrations, the support for these will be removed soon. The following APIs will be affected. * [Search API](/docs/api/v1/search/search) * [Tasks API](/docs/api/v1/tasks-call-control/get-tasks) * [Get Agent Activities](/docs/api/v1/agents/get-agent-activities) * [Get Agent Statistics](/docs/api/v1/agents/get-agent-statistics) * [Get Queue Statistics](/docs/api/v1/queue-statistics/get-queue-statistics) * [Get Estimated Wait Time](/docs/api/v1/estimated-wait-time/get-estimated-wait-time)

Wed, 10 Jul 2024 00:00:00 GMT

The scopes cjp-analyzer:config_read and cjp-analyzer:read are supported by some APIs, however since these scopes cannot be provisioned for integrations, the support for these will be removed soon. The following APIs will be affected.

Search API
Tasks API
Get Agent Activities
Get Agent Statistics
Get Queue Statistics
Get Estimated Wait Time

xml API authentication

Fri, 28 Jun 2024 00:00:00 GMT

Due to security concerns the Webex XML API won't support username/email+password authentication effective Nov 30, 2024 for CI native organizations (organizations managed through Control Hub only). Instead authentication must happen via the Common Identity system and the use of session login ticket. As a reminder the Webex XML API has been End of Life and End of Service since March 31, 2024. Some customers got an extension.

Starting from July 19th, 2024, a new field, `Location_ID`, will be added to the [Wholesale Billing Reports](/docs/api/v1/wholesale-billing) API, and this applies to both Customer and User report types.

Thu, 27 Jun 2024 00:00:00 GMT

Starting from July 19th, 2024, a new field, Location_ID, will be added to the Wholesale Billing Reports API, and this applies to both Customer and User report types.

Starting August 12th, 2024, the `callingLineId` and `routingProfile` fields will be removed from the [Test Call Routing](/docs/api/v1/call-routing/test-call-routing) endpoint's response payload.

Thu, 27 Jun 2024 00:00:00 GMT

Starting August 12th, 2024, the callingLineId and routingProfile fields will be removed from the Test Call Routing endpoint's response payload.

meetingTranscripts don't work with AI Assistant

Mon, 24 Jun 2024 00:00:00 GMT

The meeting transcripts endpoint will not have data for meetings where the Webex AI Assistant is part of the meeting and instead the recordings transcripts must be used. For further information, please see here.

As a Compliance Officer, you can now access Webex Calling recordings using the [Converged Recordings](/docs/api/v1/converged-recordings) API. You can [List Recordings for Compliance officer](/docs/api/v1/converged-recordings/list-recordings-for-compliance-officer), [Get Recording Details](/docs/api/v1/converged-recordings/get-recording-details), [Delete a Recording](/docs/api/v1/converged-recordings/delete-a-recording), and [Get Recording metadata](/docs/api/v1/converged-recordings/get-recording-metadata).

Tue, 18 Jun 2024 00:00:00 GMT

As a Compliance Officer, you can now access Webex Calling recordings using the Converged Recordings API. You can List Recordings for Compliance officer, Get Recording Details, Delete a Recording, and Get Recording metadata.

The Agent Profile APIs will be replaced with [Desktop Profile APIs](/docs/api/v1/desktop-profile). All operations done with Agent Profile APIs will be possible with [Desktop Profile APIs](/docs/api/v1/desktop-profile).

Wed, 12 Jun 2024 00:00:00 GMT

The Agent Profile APIs will be replaced with Desktop Profile APIs. All operations done with Agent Profile APIs will be possible with Desktop Profile APIs.

In the [Workspace Call Settings](/docs/api/v1/workspace-call-settings) API, we've added multiple endpoints that let you manage all Professional Workspace call settings.

Thu, 30 May 2024 00:00:00 GMT

In the Workspace Call Settings API, we've added multiple endpoints that let you manage all Professional Workspace call settings.

The [Auxiliary Codes APIs](/docs/api/v1/auxiliary-code) have been updated to support the inclusion of the `burnoutInclusion` property

Thu, 30 May 2024 00:00:00 GMT

The Auxiliary Codes APIs have been updated to support the inclusion of the burnoutInclusion property

The [Users APIs](/docs/api/v1/users) have been updated to support the inclusion of the `userLevelBurnoutInclusion` property

Thu, 30 May 2024 00:00:00 GMT

The Users APIs have been updated to support the inclusion of the userLevelBurnoutInclusion property

[Bulk partial update Users](/docs/api/v1/users/bulk-partial-update-users) has been added to conveniently update the entity by passing in only the properties that need updating.

Thu, 30 May 2024 00:00:00 GMT

Bulk partial update Users has been added to conveniently update the entity by passing in only the properties that need updating.

[Bulk partial update Auxiliary Codes](/docs/api/v1/auxiliary-code/bulk-partial-update-auxiliary-codes) has been added to conveniently update the entity by passing in only the properties that need updating.

Thu, 30 May 2024 00:00:00 GMT

Bulk partial update Auxiliary Codes has been added to conveniently update the entity by passing in only the properties that need updating.