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.

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

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 API. Additionally, the Initiate Move Users Job has now been enhanced to support non-calling user moves.

Admins can now update the ownerID in a request when using Reassign Recordings 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.

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

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.

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.

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.

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:

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

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.

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.

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.

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.

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.

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.

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.

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.

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

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

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.

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

If a Broadworks Subscriber exists but contains errors, the Get A Broadworks Subscriber and List Broadworks Subscribers APIs now return the errorCode as integer in the errors array. This change aligns the APIs with current documentation. Please review and prepare any code using these APIs and parsing the errorCode for the change in type.

We are proud to announce the availability of the new guest creation mechanism via Service Apps. Guests are now created from authorized Service Apps with guest-issuer scopes. The traditional way of using a Guest Issuer app type is deprecated and will be removed in the future.

In the Virtual Line Call Settings API, we've added multiple endpoints that let you create and manage Virtual Lines and subsets of their call settings.

We are please to announce the support for the System for cross-domain Identity Management (SCIM) v2.0 standard as specified by RFC7643 and IETF RFC7644 in our developer program. Endpoints supported include v2/Users, v2/Groups and v2/Bulk. With Webex SCIM 2.0 APIs, customers can configure or develop SCIM 2.0 clients to manage users and groups in Webex.

The /v1/devices APIs and /v1/workspaces are moving towards returning organizations, location, and people IDs which exactly match those IDs returned by /v1/organizations, /v1/locations, and /v1/people respectively. The default format of IDs returned will be changed to the new, compatible style on February 2, 2024. Clients that rely on the current style of IDs can pass the legacy=true query parameter which will ensure the current style of organizations, location, and people IDs will continue to be returned by these APIs after the default ID style changes. Note that Webex Calling specific APIs already return IDs in the compatible format, and will not honor the legacy query parameter. APIs will continue to accept both styles of IDs.

We now provide businessTexts a.k.a. SMS events in the events API . When a Webex Calling user sends or receives SMS messages, these will be logged in the API and can be retrieved by a Compliance Officer. This feature complements our recently released CDR events.

In an ongoing effort to strengthen the security posture of the Webex Developer APIs have we removed support for the below weak and old ciphers in TLS connections. Remember only TLS 1.2 and TLS 1.3 are supported. In addition TLS SNI, Server Name Indication is now mandatory.

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA

If a Broadworks Subscriber exists but contains errors, the Get A Broadworks Subscriber and List Broadworks Subscribers APIs currently return the errorCode as a String in the errors array. From February 1 2024, these APIs will return the errorCode as an integer, which will align the APIs with current documentation. Please review and prepare any code using these APIs and parsing the errorCode for the change in type.

The API, Activate phone numbers in a location, supports a maximum of 500 phone numbers.

The APIs Add Phone Numbers to a location, Activate Phone Numbers in a location, and Remove phone numbers from a location now require phone numbers in the E.164 format for all countries.

Service Apps with meetings functionalities as indicated by meetings:* scopes can now be tied to specific sites in the organization. This selection is done by a full admin in Control Hub who authorizes the Service App for the required site(s). The admin can choose from any or all of the meetings sites in the organization. The service app can only act on the allowed sites. As an example let's assume an organization with two sites A and B. An admin wants to use a meeting scheduling Service App, but wants to allow this Service App only for site A. The admin would during the authorization process select site A and the Service App will not be able to schedule meetings on site B.

The call detaill records for Webex Calling can now be found in the /events API under the resource call_records.

The reports API provides download links for reports today in CSV format. This behavior will change on January 4, 2024 and the default file format will be zip. Until January 31, 2024 you can force the download in CSV by manipulating the download URL and setting the zipEnable=false. After January 31, 2024 this flag will be ignored and all reports will be provided in zip format only. Please see also this help article.

The Add Phone Numbers to a location endpoint now supports adding toll-free numbers via the new numberType field. The possible values for this field are DID, which is the default if not specified, and TOLLFREE. This functionality now properly validates that the location has a compatible PSTN connection type and ID set before adding numbers, and returns a HTTP 200 OK rather than HTTP 201 Created on success.

As indicated on September 13, here in this change log, we have now enacted the new license API with the new names and the http PATCH.

As part of the change we removed some license strings that had no function. These are Webex Meetings Assistant(WAM) and Meeting - Webex Collaboration Meeting Rooms (CMR).

The following fields have been added to the Webex Calling Detailed Call History report: Ring duration, Release time, Answer indicator, Final local SessionID, and Final remote SessionID.

When patching a meeting, the agenda, recurrence, and trackingCodes attributes can now be specified as null so that those attributes become null and hidden from the response after the patch. For example, by patching recurrence as null, a recurring meeting can be changed to a non-recurring meeting. Note that you must use the the keyword null not the string "null".

The Receptions client DELETE feature has been corrected to return an HTTP 404 Not Found error when the given directoryId does not exist rather than HTTP 204 No Content.

Due to a system issue, webhooks with an IP address in the targetUrl may have been disabled between Oct 13, 2023 04:30:00AM UTC and Oct 13, 2023 19:40:00 UTC. If your webhook was affected you must manually re-enable the webhook. You can do this with a PUT request and by setting the status field to active. Please see here. We apologize for this error on our side.

As described in the Meeting Transcripts API document, the meeting transcript cannot be recorded until the meeting recording is turned on. Since August 1, 2023, you not only need to turn on the meeting recording, but also need to turn on the Webex Assistant or the Closed Captions in order to record the meeting transcript.

In the Users Call Settings API, we've added Get Users Music on Hold Endpoint and Modify Users Music on Hold Endpoint that let you configure music on hold settings for individual users.

In the Workspace Call Settings API, we've added Get Workspace Music on Hold Endpoint and to Modify Workspace Music on Hold Endpoint that let you configure music on hold settings for individual workspaces.

As an admin user, you can now refresh personal room IDs for a site's meeting hosts using the Batch Refresh Personal Meeting Room ID API. The personal room IDs can be automatically refreshed according to the current personal room ID rule of the target site, or by the values specified by the admin user.

On 10/25/2023, we will be releasing the new PATCH API for license assignment as well as enhancements to the existing GET license API. You will be able to list users that are assigned a specific license, even external users. You will be able to use the PATCH command to assign all licenses, including the contact center licenses. Finally, the license names will be aligned with the names an admin can see in Control Hub for consistency and ease of use. In the table below, you will find the old and new license names. Please prepare your code to make use of the new names where needed. The name change will be effective with the rollout of the new functionality on Oct 25, 2023. The license IDs will not change.

Note: Due to some problems with the publishing system a publishing date of Sep 26, was shown between Sep 13-Sep 21. This article was published on Sep 13, 2023.

The autoAcceptRequest parameter has been added to the the request of the Update Meeting Registration Form API, and has also been added to the response of the Update Meeting Registration Form and Get registration form for a meeting APIs.

New attributes,hostEmail, and hostDisplayName are returned in the response of the List Recordings For an Admin or Compliance Officer API.

The Webex Calling Devices and Workspaces APIs now have the ability to list and add Webex Calling Workspaces and Devices, to onboard Webex Calling devices by MAC address, to manage Device Call Settings with Third-party device activation, and to manage Device Line Key templates.