Webex for Developers Changelog API

SDK Upgrade

Thu, 09 May 2024 00:00:00 GMT

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](/docs/api/v1/wholesale-provisioning). This package offers customer experience essentials with advanced group call management abilities on top of Webex calling. [Click here](https://help.webex.com/en-us/article/nkguodc/Wholesale-Route-to-Market-Solution-Guide?_gl=1j7ovxk_gaMzUwOTc5MTc5LjE2OTU3NDIyOTk._ga_KP8QEFW4MLMTcwODg4MDI2My4xNi4xLjE3MDg4ODAzMjkuNjAuMC4w_gcl_au*NjUwMjUzMjkxLjE3MDQ3OTMxOTc.) 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.

Tue, 07 May 2024 00:00:00 GMT

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.

Change to life cycle fields in people API

Tue, 07 May 2024 00:00:00 GMT

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](https://help.webex.com/en-us/article/nmug598/Reports-for-Your-Cloud-Collaboration-Portfolio#reference-template_30fd64bf-8461-4072-ab9b-e4b04894eb5b) and [Webex Calling Detailed Call History Reports API](/docs/api/v1/reports-detailed-call-history/get-detailed-call-history).

Fri, 03 May 2024 00:00:00 GMT

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](/docs/api/v1/meeting-participants/list-meeting-participants), [Query Meeting Participants with Email](/docs/api/v1/meeting-participants/query-meeting-participants-with-email), and [Get Meeting Participant Details](/docs/api/v1/meeting-participants/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](/docs/api/v1/meeting-participants/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](/docs/api/v1/meetings/list-meeting-breakout-sessions) can now return the breakout sessions which happened during that meeting instance.

Fri, 26 Apr 2024 00:00:00 GMT

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.

service app authorization webhooks

Tue, 23 Apr 2024 00:00:00 GMT

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](/docs/api/v1/wholesale-provisioning/provision-a-wholesale-subscriber), [PUT](/docs/api/v1/wholesale-provisioning/update-a-wholesale-subscriber), [GET](/docs/api/v1/wholesale-provisioning/get-a-wholesale-subscriber), [LIST](/docs/api/v1/wholesale-provisioning/list-wholesale-subscribers) and [PreCheck](/docs/api/v1/wholesale-provisioning/precheck-a-wholesale-subscriber-provisioning) APIs on the 10th May, 2024.

Wed, 17 Apr 2024 00:00:00 GMT

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](/docs/api/v1/user-call-settings/retrieve-list-of-call-queue-caller-id-information), [Retrieve a Call Queue Agent's Caller ID information](/docs/api/v1/user-call-settings/retrieve-a-call-queue-agent's-caller-id-information), and [Modify a Call Queue Agent's Caller ID information](/docs/api/v1/user-call-settings/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](/docs/api/v1/user-call-settings/retrieve-agent's-list-of-available-caller-ids), [Retrieve Agent's Caller ID Information](/docs/api/v1/user-call-settings/retrieve-agent's-caller-id-information), and [Modify Agent's Caller ID Information](/docs/api/v1/user-call-settings/modify-agent's-caller-id-information) respectively.

Tue, 02 Apr 2024 00:00:00 GMT

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.

Mandatory SDK Upgrade

Mon, 25 Mar 2024 00:00:00 GMT

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](/docs/api/v1/meetings/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.

Wed, 20 Mar 2024 00:00:00 GMT

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](/docs/api/v1/wholesale-provisioning/provision-a-wholesale-subscriber), [PUT](/docs/api/v1/wholesale-provisioning/update-a-wholesale-subscriber), [GET](/docs/api/v1/wholesale-provisioning/get-a-wholesale-subscriber), [LIST](/docs/api/v1/wholesale-provisioning/list-wholesale-subscribers) and [PreCheck](/docs/api/v1/wholesale-provisioning/precheck-a-wholesale-subscriber-provisioning) APIs. Further information will be provided well in advance of a published removal date.

Mon, 18 Mar 2024 00:00:00 GMT

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.

access_token POST via body

Fri, 15 Mar 2024 00:00:00 GMT

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.

Calling API ID changes

Thu, 14 Mar 2024 00:00:00 GMT

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](/docs/api/v1/virtual-line-call-settings) API, we've added multiple endpoints that let you manage all Virtual Lines call settings.

Fri, 08 Mar 2024 00:00:00 GMT

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

ID normalization for Person's Privacy Settings

Thu, 07 Mar 2024 00:00:00 GMT

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.

Call forwarding changes

Thu, 07 Mar 2024 00:00:00 GMT

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](/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). 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.

Wed, 06 Mar 2024 00:00:00 GMT

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](/docs/api/v1/location-call-settings/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.

Tue, 27 Feb 2024 00:00:00 GMT

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.

Wed, 21 Feb 2024 00:00:00 GMT

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](/docs/api/v1/broadworks-subscribers/get-a-broadworks-subscriber) and [List Broadworks Subscribers](/docs/api/v1/broadworks-subscribers/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.

Wed, 07 Feb 2024 00:00:00 GMT

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.

Guests via Service Apps

Wed, 31 Jan 2024 00:00:00 GMT

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](/docs/api/v1/virtual-line-call-settings) API, we've added multiple endpoints that let you create and manage Virtual Lines and subsets of their call settings.

Thu, 25 Jan 2024 00:00:00 GMT

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.

SCIM v2 Support

Wed, 17 Jan 2024 00:00:00 GMT

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.

Id's in calling

Thu, 21 Dec 2023 00:00:00 GMT

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.

SMS Events

Fri, 15 Dec 2023 00:00:00 GMT

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.

Weak Obsolete Cipher Removal

Tue, 12 Dec 2023 00:00:00 GMT

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](/docs/api/v1/broadworks-subscribers/get-a-broadworks-subscriber) and [List Broadworks Subscribers](/docs/api/v1/broadworks-subscribers/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.

Tue, 12 Dec 2023 00:00:00 GMT

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](/docs/api/v1/numbers/activate-phone-numbers-in-a-location), supports a maximum of 500 phone numbers.

Wed, 06 Dec 2023 00:00:00 GMT

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

The APIs [Add Phone Numbers to a location](/docs/api/v1/numbers/add-phone-numbers-to-a-location), [Activate Phone Numbers in a location](/docs/api/v1/numbers/activate-phone-numbers-in-a-location), and [Remove phone numbers from a location](/docs/api/v1/numbers/remove-phone-numbers-from-a-location) now require phone numbers in the E.164 format for all countries.

Wed, 06 Dec 2023 00:00:00 GMT

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

Thu, 30 Nov 2023 00:00:00 GMT

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.

Call Detail Records in /events API

Fri, 17 Nov 2023 00:00:00 GMT

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

Reports default file format as zip

Thu, 16 Nov 2023 00:00:00 GMT

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](/docs/api/v1/numbers/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.

Sun, 12 Nov 2023 00:00:00 GMT

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.

new PATCH license API now released

Wed, 01 Nov 2023 00:00:00 GMT

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](/docs/api/v1/reports-detailed-call-history/get-detailed-call-history): Ring duration, Release time, Answer indicator, Final local `SessionID`, and Final remote `SessionID`.

Fri, 27 Oct 2023 00:00:00 GMT

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

Wed, 25 Oct 2023 00:00:00 GMT

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

Delete returns 404 for Receptionist if resource doe not exist

Mon, 23 Oct 2023 00:00:00 GMT

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.

Reactivate webhooks with IP addresses in targetUrl

Fri, 13 Oct 2023 00:00:00 GMT

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](/docs/api/v1/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](https://www.cisco.com/c/en/us/products/collateral/conferencing/webex-meetings/at-a-glance-c45-744053.html) or the [Closed Captions](https://help.webex.com/en-us/article/lzi8h2/Show-or-hide-automated-closed-captions-during-a-Webex-meeting-or-webinar) in order to record the meeting transcript.

Thu, 12 Oct 2023 00:00:00 GMT

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](/docs/api/v1/user-call-settings) API, we've added [Get Users Music on Hold Endpoint](/docs/api/v1/user-call-settings/retrieve-music-on-hold-settings-for-a-person) and [Modify Users Music on Hold Endpoint](/docs/api/v1/user-call-settings/configure-music-on-hold-settings-for-a-person) that let you configure music on hold settings for individual users.

Wed, 04 Oct 2023 00:00:00 GMT

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](/docs/api/v1/workspace-call-settings/) API, we've added [Get Workspace Music on Hold Endpoint](/docs/api/v1/workspace-call-settings/retrieve-music-on-hold-settings-for-a-workspace) and to [Modify Workspace Music on Hold Endpoint](/docs/api/v1/workspace-call-settings/configure-music-on-hold-settings-for-a-workspace) that let you configure music on hold settings for individual workspaces.

Wed, 04 Oct 2023 00:00:00 GMT

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](/docs/api/v1/meeting-preferences/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.

Wed, 27 Sep 2023 00:00:00 GMT

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.

The `autoAcceptRequest` parameter has been added to the the request of the [Update Meeting Registration Form](/docs/api/v1/meetings/update-meeting-registration-form) API, and has also been added to the response of the [Update Meeting Registration Form](/docs/api/v1/meetings/update-meeting-registration-form) and [Get registration form for a meeting](/docs/api/v1/meetings/get-registration-form-for-a-meeting) APIs.

Wed, 13 Sep 2023 00:00:00 GMT

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 license names in Payload for licensing API

Wed, 13 Sep 2023 00:00:00 GMT

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.

Offer code	Existing name	New name
MS	Messaging	Advance Messaging
CF	Meeting 25 party	Advanced Space Meetings
EE	Meeting - Webex Enterprise Edition	Webex Meetings Suite
MC	Meeting - Webex Meeting Center	Webex Meetings
SC	Meeting - Webex Support Center	Webex Support
TC	Meeting - Webex Training Center	Webex Training
EC	"Meeting - Webex Event Center	Webex Webinar
WXSFREE	Webex Free Meetings	Basic Meetings
CO	Calling	Webex Calling
SD	Room Systems	Webex Room Kit
EC250	Webex Events 250	Webex Webinar 250
EC500	Webex Events 500	Webex Webinar 500
EC1k	Webex Events 1000	Webex Webinar 1000
EC3k	Webex Events 3000	Webex Webinar 3000
EC5k	Webex Events 5000	Webex Webinar 5000
EC10k	Webex Events 10000	Webex Webinar 10000
EC25k	Webex Events 25000	Webex Webinar 25000
EC50k	Webex Events 50000	Webex Webinar 50000
EC100k	Webex Events 100000	Webex Webinar 100000
RTT	Webex Real-Time Translations	Real-Time Translations
FMS	Basic message	Basic Messaging
FTS	Call on Webex	Call on Webex (1:1 call, non-PSTN)
FTM	Basic meeting	Basic Space Meetings
UCPREM	On-Prem UCM Calling	Unified Communication Manager (UCM)
CVI	MS Teams Video	Webex Video Integration for Microsoft Teams
CJPPRM	CJP Premium	Contact Center Premium Agent3

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.

New attributes,`hostEmail`, and `hostDisplayName` are returned in the response of the [List Recordings For an Admin or Compliance Officer](/docs/api/v1/recordings/list-recordings-for-an-admin-or-compliance-officer) API.

Thu, 07 Sep 2023 00:00:00 GMT

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](/docs/api/v1/devices](/docs/api/v1/devices) and [Workspaces](/docs/api/v1/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.

Thu, 31 Aug 2023 00:00:00 GMT

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.

When the feature toggle `DecoupleJBHWithRegistration` is applied, the `Join Before Host` option can be enabled for meetings with registration. As a meeting host, cohost, attendee, guest, or guest issue user, you can retrieve the meeting start or join links using the [Join a Meeting](/docs/api/v1/meetings/join-a-meeting) API. NOTE: If the meeting is webinar-enabled and includes the `registration ID` option, the `registrationId` parameter is required.

Mon, 28 Aug 2023 00:00:00 GMT

When the feature toggle DecoupleJBHWithRegistration is applied, the Join Before Host option can be enabled for meetings with registration. As a meeting host, cohost, attendee, guest, or guest issue user, you can retrieve the meeting start or join links using the Join a Meeting API. NOTE: If the meeting is webinar-enabled and includes the registration ID option, the registrationId parameter is required.

The [Create a Meeting](/docs/api/v1/meetings-with-audio-watermark/create-a-meeting), [Patch a Meeting](/docs/api/v1/meetings-with-audio-watermark/patch-a-meeting), and [Update a Meeting](/docs/api/v1/meetings-with-audio-watermark/update-a-meeting) APIs now have an attribute named `enabledAudioWatermark` that allows you to specify whether to turn on meeting audio watermarking. Only specific users can use the function. Please contact an administrator to enable the required feature toggle. Webex version 43.9.0 or higher is required.

Thu, 24 Aug 2023 00:00:00 GMT

The Create a Meeting, Patch a Meeting, and Update a Meeting APIs now have an attribute named enabledAudioWatermark that allows you to specify whether to turn on meeting audio watermarking. Only specific users can use the function. Please contact an administrator to enable the required feature toggle. Webex version 43.9.0 or higher is required.

TimeZone

Wed, 09 Aug 2023 00:00:00 GMT

In the locations API we will now support the field name timeZone instead of timezone to adhere to Cisco's API standards and avoid customer confusion. This change will be effective Sep 21, 2023.

A webinar host can now generate individual post-event survey links for different users using the [Get Meeting Survey Links](/docs/api/v1/meetings/get-meeting-survey-links) API by specifying users' emails. This API only applies to webinars. Webex version 43.8.0 or higher is required.

Thu, 27 Jul 2023 00:00:00 GMT

A webinar host can now generate individual post-event survey links for different users using the Get Meeting Survey Links API by specifying users' emails. This API only applies to webinars. Webex version 43.8.0 or higher is required.

In the [User Call Settings](/docs/api/v1/user-call-settings) APIs, new APIs to [Get Users Preferred Answer Endpoint](/docs/api/v1/user-call-settings/get-preferred-answer-endpoint) and to [Modify Users Preferred Answer Endpoint](/docs/api/v1/user-call-settings/modify-preferred-answer-endpoint) have been added. In the [Call Controls](/docs/api/v1/call-controls) APIs, the [dial](/docs/api/v1/call-controls/dial), [answer](/docs/api/v1/call-controls/answer), [retrieve](/docs/api/v1/call-controls/retrieve), [pickup](/docs/api/v1/call-controls/pickup) and [barge-in](/docs/api/v1/call-controls/barge-in) APIs have been enhanced to include an optional `endpointId` attribute. You can choose to use the `Modify Users Preferred Answer Endpoint` API to specify the preferred answer endpoint for all subsequent calls or instead specify the endpointId for each call using the Call Control API option.

Thu, 27 Jul 2023 00:00:00 GMT

In the User Call Settings APIs, new APIs to Get Users Preferred Answer Endpoint and to Modify Users Preferred Answer Endpoint have been added. In the Call Controls APIs, the dial, answer, retrieve, pickup and barge-in APIs have been enhanced to include an optional endpointId attribute. You can choose to use the Modify Users Preferred Answer Endpoint API to specify the preferred answer endpoint for all subsequent calls or instead specify the endpointId for each call using the Call Control API option.

More granular parameters in Configure Call Recording Settings

Fri, 21 Jul 2023 00:00:00 GMT

In the Configure Call Recording Settings for a Person API we are phasing out the startStopAnnouncementEnabled parameter and replace it with more granular control. The setting can now be configured for internal calls and pstn calls separately. The respective parameters are startStopAnnouncement.internalCallsEnabled and startStopAnnouncement.pstnCallsEnabled. You can use the new parameters immediately.

As a host or cohost user, you can now list in-progress meeting breakout sessions using the [List Meeting Breakout Sessions](/docs/api/v1/meetings/list-meeting-breakout-sessions) API and admit participants into meeting breakout sessions using [Admit Participants](/docs/api/v1/meeting-participants/admit-participants). The changes only apply to meetings on converged sites and are behind a feature toggle. Only EFT users can use the functions. Please contact an administrator to enable the feature toggle. Webex version 43.6.0 or higher is required.

Tue, 18 Jul 2023 00:00:00 GMT

As a host or cohost user, you can now list in-progress meeting breakout sessions using the List Meeting Breakout Sessions API and admit participants into meeting breakout sessions using Admit Participants. The changes only apply to meetings on converged sites and are behind a feature toggle. Only EFT users can use the functions. Please contact an administrator to enable the feature toggle. Webex version 43.6.0 or higher is required.

The `numbers` and `mainNumber` attributes in the following Wholesale APIs: [Provision a Wholesale Customer](/docs/api/v1/wholesale-customers/provision-a-wholesale-customer), [Update a Wholesale Customer](/docs/api/v1/wholesale-customers/update-a-wholesale-customer), and [Precheck a Wholesale Customer Provisioning](/docs/api/v1/wholesale-customers/precheck-a-wholesale-customer-provisioning) will be deprecated in the near future.

Thu, 06 Jul 2023 00:00:00 GMT

The numbers and mainNumber attributes in the following Wholesale APIs: Provision a Wholesale Customer, Update a Wholesale Customer, and Precheck a Wholesale Customer Provisioning will be deprecated in the near future.

Enormous Announcement API ChangeLog Entry

Thu, 06 Jul 2023 00:00:00 GMT

We've added support for an "announcement repository", which is a centralized repository of media at the customer/org and location levels. Different features can utilize this media for things like audible announcements being played when certain events/situations happen. The following APIs can upload and list announcements at the customer or org level: Upload a binary announcement greeting at organization level, Fetch list of announcement greetings on location and organization level, Fetch details of binary announcement greeting at organization level, Modify a binary announcement greeting, Fetch repository usage for announcements for an organization, and Delete an announcement greeting of an organization. The following APIs can upload and list announcements at the location level: Upload a binary announcement greeting at the location level, Fetch details of binary announcement greeting at location level, Modify a binary announcement greeting, Fetch repository usage for announcements in a location, and Delete an announcement greeting in a location The remaining APIs are modified to allow referencing the files in the announcement repository (updated with the audioAnnouncementFiles array): Create a call queue, Get details for a call queue, Update a call queue, Read the list of call queue announcement files, Get details for an auto attendant, Create an auto attendant, Update an auto attendant, Get music on hold, Update music on hold, Get details for a call queue forced forward service, Update a call queue forced forward service, Get details for a call queue holiday service, Update a call queue holiday service, Get details for a call queue night service, Update a call queue night service, Get details for a call queue stranded calls, and Update a call queue stranded calls service.

[Webex Calling detailed call history API CDR feed](/docs/api/v1/webex-calling-detailed-call-history/get-detailed-call-history) is included with additional "Reasons" and "User type" attributes, clarifying user types and call reasons that can be initiated, terminated or redirected. For more details about these new attributes see [Detailed call history API](/docs/api/v1/webex-calling-detailed-call-history/get-detailed-call-history), or [Webex Calling reports for your collaboration portfolio](https://help.webex.com/en-us/article/nmug598/Reports-for-Your-Cloud-Collaboration-Portfolio).

Wed, 28 Jun 2023 00:00:00 GMT

Webex Calling detailed call history API CDR feed is included with additional "Reasons" and "User type" attributes, clarifying user types and call reasons that can be initiated, terminated or redirected. For more details about these new attributes see Detailed call history API, or Webex Calling reports for your collaboration portfolio.

HTML support in /messages

Wed, 28 Jun 2023 00:00:00 GMT

We do now support limited HTML markup in message creation and edits. The supported HTML tags are limited to h1,h2,h3,ul,ol,u,i,b and links href.

Calls API EOL

Wed, 28 Jun 2023 00:00:00 GMT

Some customers and partners were provided with early beta (limited) access to a REST API and webhooks for space calls and meetings. The API is known in the field as calls-api. This API was never publicly available, and all production use was discouraged. We are going to shut down this API by Sep 30, 2023. The calls-api mentioned here is not connected to CUCM, Webex Calling, or Broadworks which we will continue to carry forward and extend their functionality. If you are interested in webhooks for meetings see the meetings resource in the webhooks guide and the meetings API. If you are interested in calling webhooks please see the telephony_calls resource in the webhooks guide and the calling API. If you are interested in Webex Calling records, please see the Webex Calling CDR API

The Meetings API now supports the following options: requiring attendees to sign in before joining a webinar and restricting the webinar to invited attendees only. The following endpoints now support the parameters `requireAttendeeLogin` and `restrictToInvitees`: [Create a Meeting](/docs/api/v1/meetings/create-a-meeting), [Get a Meeting](/docs/api/v1/meetings/get-a-meeting), and [List Meetings](/docs/api/v1/meetings/list-meetings), and [Get a Meeting Template](/docs/api/v1/meetings/get-a-meeting-template).

Tue, 20 Jun 2023 00:00:00 GMT

The Meetings API now supports the following options: requiring attendees to sign in before joining a webinar and restricting the webinar to invited attendees only. The following endpoints now support the parameters requireAttendeeLogin and restrictToInvitees: Create a Meeting, Get a Meeting, and List Meetings, and Get a Meeting Template.

no null values

Tue, 20 Jun 2023 00:00:00 GMT

In the Webex Calling APIs we will not return fields with null values any longer to be consistent with the rest of our API set. Fields that have a null value will be omitted from the response. This change will be enforced on August 1, 2023.

The [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 now support querying ended meeting instances with the following meeting feature flags: `hasChat`, `hasRecording`, `hasTranscription`, `hasClosedCaption`, `hasPolls`, and `hasQA`.

Mon, 05 Jun 2023 00:00:00 GMT

The List Meetings and List Meetings of a Meeting Series APIs now support querying ended meeting instances with the following meeting feature flags: hasChat, hasRecording, hasTranscription, hasClosedCaption, hasPolls, and hasQA.

The [Get Recording Details](/docs/v1/recordings/get-recording-details) API now supports the ARF recording format.

Thu, 25 May 2023 00:00:00 GMT

The Get Recording Details API now supports the ARF recording format.

As an Compliance Officer, you are always allowed to retrieve `temporaryDirectDownloadLinks` using the [Get Recording Details](/docs/v1/recordings/{recordingId} API, even if the recording is flagged to prevent downloads.

Wed, 10 May 2023 00:00:00 GMT

As an Compliance Officer, you are always allowed to retrieve temporaryDirectDownloadLinks using the [Get Recording Details](/docs/v1/recordings/{recordingId} API, even if the recording is flagged to prevent downloads.

Service Apps are now GA

Thu, 13 Apr 2023 00:00:00 GMT

Service Apps are now Generally Available. Service Apps are a new application type, accessible to developers under 'Create a New App.' Service Apps follow a 2-step process with a developer creating an app and an admin authorizing the app in Control Hub. The result is a forever-lived machine account in the authorizing org on whose behalf API calls are made. This means you don't risk your mission-critical apps stopping just because the authorizing user left or changed their password. For more information, please see here.

A new attribute,`startLink`, has been added to the [Join a Meeting](/docs/api/v1/meetings/join-a-meeting) API. The `startLink` attribute can be used to start a meeting as the meeting host. Only the meeting host or cohost can generate a `startLink`.

Wed, 12 Apr 2023 00:00:00 GMT

A new attribute,startLink, has been added to the Join a Meeting API. The startLink attribute can be used to start a meeting as the meeting host. Only the meeting host or cohost can generate a startLink.

As an admin user, you can now reassign meetings to a new host using the [Reassign Meetings to a New Host](/docs/api/v1/meetings/reassign-meetings-to-a-new-host) API with a `hostEmail` and a group of `meetingIds`. This new API applies to Webex client 43.4.0 or higher.

Mon, 27 Mar 2023 00:00:00 GMT

As an admin user, you can now reassign meetings to a new host using the Reassign Meetings to a New Host API with a hostEmail and a group of meetingIds. This new API applies to Webex client 43.4.0 or higher.

The issue where the ['Get a List of Phone Numbers for a Person'](/docs/api/v1/webex-calling-person-settings/get-a-list-of-phone-numbers-for-a-person) API doesn't return the `directNumber` in industry standard E164 format has been fixed. Clients expecting the original format using the `GET /v1/people/{userId}/features/numbers` API may need to be updated.

Mon, 20 Mar 2023 00:00:00 GMT

The issue where the 'Get a List of Phone Numbers for a Person' API doesn't return the directNumber in industry standard E164 format has been fixed and will be rolled out and enforced on May 3, 2023. Clients expecting the original format using the GET /v1/people/{userId}/features/numbers API may need to be updated.

A new attribute, `spEnterpriseGroupId`, has been added to the [Provision a Broadworks Subscriber](/docs/api/v1/broadworks-subscribers/provision-a-broadworks-subscriber) and the [Update a Broadworks Subscriber]( /docs/api/v1/broadworks-subscribers/update-a-broadworks-subscriber) APIs, for partners with the `w4bwks-group-contacts-support` toggle. These APIs allow group provisioning for Enterprise for Webex For Broadworks users. For additional information, see the [Group Contacts Support](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wx4bwks/Solution_Guide/wbxbw_b_solution-guide.pdf) section of the Webex For BroadWorks Solution Guide.

Tue, 07 Mar 2023 00:00:00 GMT

A new attribute, spEnterpriseGroupId, has been added to the Provision a Broadworks Subscriber and the Update a Broadworks Subscriber APIs, for partners with the w4bwks-group-contacts-support toggle. These APIs allow group provisioning for Enterprise for Webex For Broadworks users. For additional information, see the Group Contacts Support section of the Webex For BroadWorks Solution Guide.

For security and maintainability reasons, the recordings SOAP API will be deprecated as of Jan 1, 2023, and should not be used for any new projects. On June 30, 2023, the recordings SOAP API will be permanently shut down. To facilitate the migration to alternative REST APIs, two more admin-level recording report APIs are provided. As an admin user, you can now [list meeting archive summaries](/docs/api/v1/recording-report/list-meeting-archive-summaries) with a time range on a target site and [get meeting archive details](/docs/api/v1/recording-report/get-meeting-archive-details) with a meeting archive ID.

Tue, 07 Mar 2023 00:00:00 GMT

In support of the SOAP API EOL/EOS that was announced on December 27, 2022, on this changelog we provide two more admin-level recording APIs for our customers to seamlessly transfer their workflows. As an admin user, you can now list meeting archive summaries with a time range on a target site and get meeting archive details with a meeting archive ID.

As an admin user or a normal meeting host, you can now [list meeting attendee reports](/docs/api/v1/meetings-summary-report/list-meeting-attendee-reports) on a site. The meeting attendee reports include aggregated meeting attendee information, such as `joinedTime`, `leftTime`, `duration`, etc.

Fri, 17 Feb 2023 00:00:00 GMT

As an admin user or a normal meeting host, you can now list meeting attendee reports on a site. The meeting attendee reports include aggregated meeting attendee information, such as joinedTime, leftTime, duration, etc.

events API actor ids

Mon, 13 Feb 2023 00:00:00 GMT

The events API has an undocumented, unadvertised, and never publicized feature to query events for several actor Ids in a single GET request. Due to architectural changes, we cannot honor these queries any longer and will return a 400 error. This behavior will be enforced on March 31, 2023.

The [Update a Meeting](/docs/api/v1/meetings/update-a-meeting) API PUT method is still supported and behaves the same as before, but will be deprecated in the furture. Use the [Patch a Meeting](/docs/api/v1/meetings/patch-a-meeting) API via the PATCH method as a replacement.

Thu, 09 Feb 2023 00:00:00 GMT

The Update a Meeting PUT method is still supported and behaves the same as before, but has been deprecated. Use the Patch a Meeting via the PATCH method as a replacement.

A new attribute of `expirationMinutes` is added to the [Join a Meeting](/docs/api/v1/meetings/join-a-meeting) API to specify when the join meeting link expires.

Thu, 09 Feb 2023 00:00:00 GMT

A new attribute, expirationMinutes, has been added to the Join a Meeting API to specify when the join meeting link expires.

A new attribute, `panelist`, has been added to the `invitees` for the [Create a Meeting](/docs/api/v1/meetings/create-a-meeting) API. This new attribute only applies to webinars, not meeting.

Thu, 09 Feb 2023 00:00:00 GMT

A new attribute, panelist, has been added to the invitees for the Create a Meeting API. This new attribute only applies to webinars, not meeting.

As a meeting user, you can now [create a meeting](/docs/api/v1/meetings/create-a-meeting), [update a meeting](/docs/api/v1/meetings/update-a-meeting), and [list meetings](/docs/api/v1/meetings/list-meetings) with audio connection options.

Wed, 08 Feb 2023 00:00:00 GMT

As a meeting user, you can now create a meeting, update a meeting, and list meetings with audio connection options.

As an admin user, you can now [list meeting usage reports](/docs/api/v1/meetings-summary-report/list-meeting-usage-reports) on a site. The meeting usage reports include aggregated meeting usage information, such as `totalCallInMinutes`, `totalParticipants`, etc. It also includes the meeting `trackingCodes`.

Wed, 18 Jan 2023 00:00:00 GMT

As an admin user, you can now list meeting usage reports on a site. The meeting usage reports include aggregated meeting usage information, such as totalCallInMinutes, totalParticipants, etc. It also includes the meeting trackingCodes.

The following three APIs now support specifying whether to send email to registrants: [Register Meeting Registrant](/docs/api/v1/meetings/register-a-meeting-registrant), [Batch Register Meeting Registrants](/docs/api/v1/meetings/batch-register-meeting-registrants), and [Batch Update Meeting Registrants status](/docs/api/v1/meetings/batch-update-meeting-registrants-status).

Tue, 10 Jan 2023 00:00:00 GMT

The following three APIs now support specifying whether to send email to registrants: Register Meeting Registrant, Batch Register Meeting Registrants, and Batch Update Meeting Registrants status.

The `participantEmail` parameter which was used to [list meetings](/docs/api/v1/meetings/list-meetings) by a meeting participant email address is no longer supported. It's been removed from the API document.

Thu, 05 Jan 2023 00:00:00 GMT

The participantEmail parameter which was used to list meetings by a meeting participant email address is no longer supported. It's been removed from the API document.

EOL SOAP Recordings API

Tue, 27 Dec 2022 00:00:00 GMT

Due to reasons of security and maintainability we are going to deprecate the recordings SOAP API. In effect Jan 1, 2023 the recordings SOAP API is being deprecated and should not be used for any new projects. On June 30, 2023 the recordings SOAP API will be permanently shut down. This means customers have a full 6 months to migrate from the current recordings SOAP API to the alternative REST APIs. Depending on your use cases we recommend using the /recordings REST resource. Other functionality in the current SOAP API is replaced by the following APIs: Meeting Participants, Meetings Chat, Meetings Polls, Meetings Q&A

New attribute `extension`, has been added to [POST Broadworks Subscriber](/docs/api/v1/broadworks-subscribers/provision-a-broadworks-subscriber) and [PUT Broadworks Subscriber](https://developer.webex.com/docs/api/v1/broadworks-subscribers/update-a-broadworks-subscriber) APIs. This attribute allows the provisioning of extension numbers for Webex For Broadworks users. For additional information, see Extension Dialing in the [Ordering and Provisioning](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wx4bwks/Solution_Guide/wbxbw_b_solution-guide/wbxbw_b_SolutionGuide-PDF_chapter_00.html#id_136799) section of the Webex For BroadWorks Solution Guide.

Thu, 08 Dec 2022 00:00:00 GMT

New attribute extension, has been added to POST Broadworks Subscriber and PUT Broadworks Subscriber APIs. This attribute allows the provisioning of extension numbers for Webex For Broadworks users. For additional information, see Extension Dialing in the Ordering and Provisioning section of the Webex For BroadWorks Solution Guide.

change to outgoing call permissions

Mon, 21 Nov 2022 00:00:00 GMT

Due to CASUAL, UNKNOWN, and URL_DIALING outgoing calling permissions not being supported for modification, these values are now ignored when the following endpoints are called:

update location outgoing permission,

modify person outgoing call permissions,

outgoing workspace permissions

These values will also be removed from the corresponding GET calls in the future and callers should not depend on these values.

Renaming of roles

Wed, 16 Nov 2022 00:00:00 GMT

We are going to rename a role in the roles API. The current Sales Administrator role will be renamed to Partner Administrator. This brings parity with the Control Hub experience and better reflects the responsibilities of the role. The Partner Administrator's privilege is to manage the specific set of customers to which they have been assigned. This change will be effective January 13, 2023.

Public spaces

Thu, 10 Nov 2022 00:00:00 GMT

We now provide the ability to create public spaces in the /rooms API. You can mark a space as public and give it a description. Public spaces are discoverable within the org. You can also update a public space to make it private if you are a member or compliance officer. The conversion from private to public is not yet supported.

The [Download Transcript](/docs/api/v1/meeting-transcripts/download-a-meeting-transcript) API no longer requires `meetingId` as a parameter.

Thu, 10 Nov 2022 00:00:00 GMT

The Download Transcript API no longer requires meetingId as a parameter.

DB backend update

Fri, 28 Oct 2022 00:00:00 GMT

We are going to update parts of our DB backend tonight Oct 28, starting at 18:30 America/Los_Angeles. There may be short service disruptions to the creation or running of applications.

Added support for creating one or more invitation sources for a meeting using the [Create Invitation Sources](/docs/api/v1/meetings/create-invitation-sources) API, and retrieving invitation sources for a meeting using the [List Invitation Sources](/docs/api/v1/meetings/list-invitation-sources) API.

Thu, 27 Oct 2022 00:00:00 GMT

Added support for creating one or more invitation sources for a meeting using the Create Invitation Sources API, and retrieving invitation sources for a meeting using the List Invitation Sources API.

As a Webex user, you can now create an ad-hoc meeting for a room by the [Create a Meeting](/docs/api/v1/meetings/create-a-meeting) API with `adhoc` of `true` and `roomId` of the target room. An ad-hoc meeting is a non-recurring instant meeting for the target room which is supposed to be started immediately after being created for a quick collaboration.

Thu, 27 Oct 2022 00:00:00 GMT

As a Webex user, you can now create an ad-hoc meeting for a room by the Create a Meeting API with adhoc of true and roomId of the target room. An ad-hoc meeting is a non-recurring instant meeting for the target room which is supposed to be started immediately after being created for a quick collaboration.

You can now [Create a Meeting](/docs/api/v1/meetings/create-a-meeting) which is associated with a Webex room using the new attribute `roomId`, and [List Meetings](/docs/api/v1/meetings/list-meetings) associated with a Webex room using the same attribute.

Thu, 27 Oct 2022 00:00:00 GMT

You can now Create a Meeting which is associated with a Webex room using the new attribute roomId, and List Meetings associated with a Webex room using the same attribute.

people API email lookup with orgId

Tue, 25 Oct 2022 00:00:00 GMT

Org admins and partner admins are able to look up people in the people API by email. Today when specifying an email and orgId, if the user is found by their email they are returned ignoring the orgId. Upon partner request, coming February 17, 2023 we will change this behavior. When a request is made with the email address and orgId provided we will return the user only when the orgId matches the orgId of the user, otherwise an empty result will be returned. Example: User A is provisioned in org A and the following query is made GET /people?email=userAemail&orgId=orgAid -> returns user A details

GET /people?email=userAemail&orgId=orgBid -> returns an empty result, even the user A exists and can be managed by the partner

Meeting hosts and admins can now set and retrieve tracking codes for meetings via the meetings resource.

Wed, 19 Oct 2022 00:00:00 GMT

Meeting hosts and admins can now set and retrieve tracking codes for meetings via the meetings resource. They can list all available tracking codes and their options by List Meeting Tracking Codes, and retrieve tracking codes for a meeting template by Get a Meeting Template.

New transcript features available.

Tue, 18 Oct 2022 00:00:00 GMT

The List Transcripts API now supports listing all transcripts for the current user at a given site, with new return parameters meetingTopic and status. Compliance Officers can now list all transcripts at a site via the new List Transcripts For Compliance officer API. Hosts and Compliance Officers now can delete specified transcripts via the new Delete Transcripts API.

Added new Site-level APIs

Wed, 12 Oct 2022 00:00:00 GMT

Introduced Webex site-level APIs into the Webex RESTful API, including Get Meeting Common Settings Configuration and Update Meeting Common Settings Configuration. These APIs let you update features, options and privileges that are configured for your Webex service sites.

Admin users can retrieve and set tracking codes for sites and users

Tue, 11 Oct 2022 00:00:00 GMT

Admins can now set and retrieve tracking codes for their managed sites and for users. Tracking codes help site administrators understand how much a particular group within an organization is using Webex services. See the help page for more details about tracking codes.

meetingParticipants join and left times

Fri, 07 Oct 2022 00:00:00 GMT

In the meetingParticipants REST resource in order to avoid race conditions and cope with the attendee behavior, where a participant rejoins the same meeting, we will not any longer provide the joinedTime and leftTime while the meeting is ongoing. Instead these fields will be correctly populated after the meeting has ended. While the meeting is ongoing you can still poll the meetingParticipants but the joinedTime and leftTime may be set to 1970-01-01T00:00:00.000Z. If you need accurate in-meeting information, that also reflects participants rejoining the meeting, please use our webhook infrastructure with the meetingParticipants resource. This change will be effective on November 20, 2022.

As an admin user, you can now [List Site Session Types](/api/v1/session-types/list-site-session-types), [List User Session Types](/api/v1/session-types/list-user-session-type), [Update User Session Types](/api/v1/session-types/update-user-session-types)

Thu, 06 Oct 2022 00:00:00 GMT

As an admin user, you can now List Site Session Types, List User Session Types, Update User Session Types.

Login with Webex additional fields

Tue, 13 Sep 2022 00:00:00 GMT

We added the following new response fields to the discovery endpoint in login with Webex (GET /v1/.well-known/openid-configuration) to increase compatibility with other systems. grant_types_supported, request_parameter_supported, request_uri_parameter_supported,token_endpoint_auth_methods_supported

Further information can be found in the Login with Webex Guide

Select Registration Criteria via API

Fri, 09 Sep 2022 00:00:00 GMT

You can now configure custom registration forms for your webinars using the /meetings registration API. The base form can be configured graphically as described here, and the API can be used to enable and disable individual elements from the master template as required by your meeting or webinar. This enhancement further increases parity between the Webex REST and XML APIs.

Compliance Officers can list [Meeting Polls](/api/v1/meeting-polls) and [Meeting Q&A](/api/v1/meeting-q-and-a). You must request access to this endpoint via our support channel.

Fri, 02 Sep 2022 00:00:00 GMT

Compliance Officers can list Meeting Polls and Meeting Q&A. You must request access to this endpoint via our support channel.

New Recycle Bin Feature

Tue, 16 Aug 2022 00:00:00 GMT

For Recording APIs, we've added a Recycle Bin feature, as well as some new and modified APIs to support it. You can move some recordings into the recycle bin using Move Recordings into Recycle Bin API. For recordings already in the recycle bin, you can choose to restore or purge them using the Restore Recordings from Recycle Bin API or the Purge Recordings from Recycle Bin API. To differentiate recordings when using List Recordings API or Admin List Recordings API, a new condition named status has been added. If available the recording is not deleted. If deleted the recording is in the recycle bin.

Deprecating language field in Broadworks Subscriber APIs

Fri, 05 Aug 2022 00:00:00 GMT

The language field from the response body of Broadworks Subscriber APIs and from the request body of Broadworks Subscriber PUT API will soon be deprecated.