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.

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

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

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.

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

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

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. 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 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: 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 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, Create a Line Key Template, and Modify a Line Key Template.

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.

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.

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 will be deprecated. Please use the List Contact Service Queues v2 API instead.

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.

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

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.

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:

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.

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.

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.

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 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 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:

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.

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 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 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 has been updated to reflect that web is the only supported value.

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

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 Create a Team API has been added.

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

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

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

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

A new version of List Contact Service Queue 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.

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

New Users APIs have been added.

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

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 (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 endpoint.

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.

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.

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 has been added.

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.

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.

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 across several environments:

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 API. Instead, this functionality will be supported through the Setup PSTN Connection for a Location API.

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, 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 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 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
• Tasks API
• Get Agent Activities
• Get Agent Statistics
• Get Queue Statistics
• Get Estimated Wait Time

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 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 endpoint's response payload.

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 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. All operations done with Agent Profile APIs will be possible with Desktop Profile APIs.

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

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

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

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

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

A Compliance Officer can now list recordings that have been purged from the recycle bin using the List Recordings For an Admin or Compliance Officer API with the status=purged parameter.

As indicated first on March 25, 2024 on this change log you must upgrade your Webex SDK version before July 1st to avoid service disruptions as customers get moved onto the Webex Suite Meetings Platform (WSMP). Alternatively you must ask for an extension by opening a support ticket. The new SDK versions allows joining a meeting via a password which is inherent to the WSMP. Please see below for the original announcement.

A progressive outbound dialer campaign is an automated system used by businesses to make outbound calls to their customers or clients. The system uses rules to determine which phone numbers to call and when to call them. Once a call is connected, the system provides the agent with information about the customer to improve service. The system can increase the productivity of call center agents, reduce wait times, and improve the customer experience.

• Create Campaign Request: A create campaign API allows businesses to programmatically create outbound campaigns using their own software applications. This type of API typically allows businesses to set up the parameters for a campaign, such as the list of phone numbers to call, the message or script to deliver, and the time of day or day of the week to call.

• Update Campaign Request: By using an update campaign API, businesses can automate the process of modifying and managing outbound campaigns, and integrate campaign updates into their existing workflows or applications. This can help to improve efficiency and reduce errors, as well as allow for greater flexibility and control over outbound campaigns.

• Delete Campaign: The delete campaign API enables businesses to automate the process of managing outbound campaigns and integrate campaign deletion into their existing workflows or applications.

We have found inconsistencies in the /people API as they relate to the invitePending and loginEnabled statuses and how they relate to the Control Hub view of users. We are going to normalize these fields in the following manner: invitePending will be a read-only field that is set and unset by our Common Identity system depending on if the user accepted the invite email. User login is allowed only after invitePending has cleared (false). loginEnabled can be set to allow or disallow users from logging in.

We will enforce this logic on or after June 10, 2024.

A new package type cx_essentials has been added to Wholesale Provisioning. This package offers customer experience essentials with advanced group call management abilities on top of Webex calling. Click here to learn more. The feature toggle wholesale-cx-essentials is required for partner admins to provision wholesale customers and users with this new package type.

Import and Export APIs have been enabled for Flows.

The Export API allows to export the draft version of a flow into a JSON file.

The Import API allows to import an exported flow and override an existing flow if there is an exact name match.

Together they enable transferring flows from one organization to another without having to change any flow config. This enables customers to test the flow in an org and import the production-ready flows into the production org.

We are updating the calculation for totalAvailableTime in the Agent Statistics API to ensure consistency across intervals, regardless of whether an agent logs out during the interval in question. Currently, totalAvailableTime is calculated as agentLoggedinDuration - unavailableDuration. This will be revised to agentIntervalStartTimeDuration - unavailableDuration.

For example, consider an agent who logs in at 2:00 PM and logs out at 2:45 PM, remaining available for 10 minutes within each 15-minute interval. We assess availability over three intervals: 2:00-2:15 PM, 2:15-2:30 PM, and 2:30-2:45 PM. The computation for the first two intervals remains unchanged. The update affects only the last interval.

Under the current method, the totalAvailableTime for the 2:30-2:45 PM window, during which the agent logged out, is incorrectly calculated as 30 minutes (10 min from 2:00 - 2:15 PM + 10 min from 2:15 - 2:30 PM + 10 min from 2:30 -2:45 PM) . After implementing the fix, the totalAvailableTime for this window i.e. 2:30 - 2:45 PM , will correctly reflect 10 minutes, aligning with the calculation used for the other intervals.

The Webex Calling Detailed Call History reporting now includes new fields that help customers identify PSTN provider details. Examples include PSTN Vendor Name, PSTN Legal Entity, and many others. For more information, see Webex Calling Reports for Your Collaboration Portfolio and Webex Calling Detailed Call History Reports API.

A new attribute breakoutSessionsAttended has been added to the List Meeting Participants, Query Meeting Participants with Email, and Get Meeting Participant Details APIs. It indicates the breakout sessions that a participant attended during a meeting, and it only applies to participants of ended meeting instances. A new parameter breakoutSessionId has been added to the List Meeting Participants API so that it can return participants who joined the specified breakout session. If the meetingId of an ended meeting instance is specified, the List Meeting Breakout Sessions can now return the breakout sessions which happened during that meeting instance.

We're pleased to introduce a new webhook resource to our Service App's framework, allowing you to receive notifications for the authorization and deauthorization of your Service Apps. This update simplifies lifecycle management and reduces the need for manual status checks. For setup instructions and more details, please visit our Webhooks Reference Page.

As previously stated in the change log published on March 18, 2024, partners should start using the new packages field, which accepts a list of packages. Cisco will be deprecating and removing the support for the existing package field in the Wholesale Subscriber Provisioning POST, PUT, GET, LIST and PreCheck APIs on the 10th May, 2024.

The Retrieve List of Call Queue Caller ID information, Retrieve a Call Queue Agent's Caller ID information, and Modify a Call Queue Agent's Caller ID information APIs are deprecated and will be decommissioned May 16, 2024. Integrations that use these APIs must move to Retrieve Agent's List of Available Caller IDs, Retrieve Agent's Caller ID Information, and Modify Agent's Caller ID Information respectively.

SDK users on versions prior to 3.11.0(iOS, Android) and prior to 2.60.0 (Browser SDK) must upgrade to these or later SDK versions by July 1st, 2024. Cisco is revamping our backend systems to the Webex Meetings Suite Platform with a mandatory password requirement to join Webex meetings. Previous SDK versions do not support this security update and you risk that your users cannot join meetings. If you cannot meet this mandatory upgrade by the designated time, please reach out to devsupport@webex.com

New attributes, createJoinLinkAsWebLink and createStartLinkAsWebLink, have been added to the Join a Meeting API which can be used to specify webLink as a joinLink or a startLink. Those are typically useful if mandatory user login is configured in Control Hub.

Partners should plan for a transition to a new packages field, which accepts a list of packages, as Cisco will eventually remove support for the existing package field in the Wholesale Subscriber Provisioning POST, PUT, GET, LIST and PreCheck APIs. Further information will be provided well in advance of a published removal date.

We have observed that during the OAuth 2.0 integration authorization process, customers have been appending data to URLs as query parameters in their POST requests. Although this method was functional previously, please be aware that it will no longer be supported after 6:00 PM on April 5, 2024 (America/Los_Angeles time zone). This change is in line with the best practices recommended by the Open Web Application Security Project (OWASP), which advises against exposing sensitive information through URL query strings (you can find more information on this topic here). We prioritize the security of your users' data, and adhering to these standards is crucial for maintaining the integrity of our platform.

On May 1, 2024, Webex Calling Public APIs are moving to a new, more modern ID for the following types: Auto Attendant, Call Queue, Hunt Group, Paging Group, and Single Number Reach. Customers following the general recommendation to treat Public API IDs opaquely should not be affected beyond comparing IDs saved in the old format with new IDs. The APIs will continue to accept ids in the old format as input.

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

The Get a person's Privacy Settings API returned IDs in the monitoringAgent field that were not compatible with APIs like Get Person Details. Get a person's Privacy Settings API has been corrected to return Person, Virtual Line, and Workspace IDs fully compatible with other APIs.

For consistency with other APIs, the GET /v1/telephony/config/locations/{locationId}/queues/{queueId}/callForwarding API will be renaming the sendToVoiceMailEnabled response field to destinationVoiceMailEnabled.

To allow API clients to make this transition, for the next six weeks, we are adding thedestinationVoiceMailEnabled alongside the existing sendToVoiceMailEnabled field. On April 15, 2024 the sendToVoiceMailEnabled will be removed from the response.

Two new attributes, hostDidJoin and attendeeDidJoin, are returned in the response of the following APIs: Get a Meeting, List Meetings, and List Meetings of a Meeting Series. Those new attributes only apply to meeting series in the inProgress state, scheduled meetings in the ready state, and meeting instances in the inProgress state, whether or not anyone has joined the meeting. Indicates that someone is waiting in the lobby and the host hasn't joined the meeting, if both attendeeDidJoin is true and hostDidJoin is false.

The below public APIs have been enhanced to enforce length restrictions on the free-form string inputs. NOTE: These changes will be GA’ed effective 29-March-2024.

The below call-control and register APIs have been enhanced to enforce length restrictions on the free-form string inputs. Please refer to the individual links for the limitations that have been added to these APIs

• create-campaign-request
• update-campaign-request
• subscribe-notification
• create-monitoring-request
• hold-task
• resume-task
• wrap-up-task
• reject-task
• consult-end-task
• consult-task
• consult-conference-task
• consult-transfer-task
• create-task
• login
• logout
• state-change
• buddy-agents-list

The Update Location Webex Calling Details API now ignores pAccessNetworkInfo if the location's country is not Belgium, Germany, and France. Starting April 11, 2024, the API will respond with an error if pAccessNetworkInfo is modified for locations outside of Belgium, Germany, and France.

Currently when one of the Webex for Wholesale or Webex for Broadworks APIs returns error code 5001, Internal Server Error, we include a description which details where the issue occurred. Since internal server errors are, by nature, unexpected, these detailed descriptions are often not useful as they reference internal service interactions beyond your control. We are now opting to return a generic description which says "An unexpected error occurred", and including an internalErrorCode in the response body to indicate the precise nature of the issue. This will help accelerate the resolution of support tickets, as an internalErrorCode is of more benefit when trying to resolve such issues. This change will take effect before the end of February.

The Search API has moved from Beta to Generally available with updated documentation and guide . There is no functional change to this API

Barge In API is introduced to create a successful barge-in request for the supervisor to barge in the call that is being monitored already.