This page lists recent and upcoming changes to the Webex Teams API. Contact Webex Developer Support with any questions.
January 26, 2021
The List BroadWorks Subscribers API now includes a
lastStatusChangequery parameter, which only includes subscribers with a provisioning status change after the specified date and time.
January 19, 2021
We now support editing of messages via API, just like you can do in the clients today. Message edits are done via PUT. Further details can be found here
January 12, 2021
We are provisioning several new types of licenses to new and existing users in support of the modular client functionality. An example of these licenses is basicMessage, basicMeeting. These will help admin's to configure or disable certain features, like message only or video only clients. These licenses are assigned in an ongoing process. As always when you do a PUT on a person, please do the GET first and replay the whole message content with your modifications.
January 11, 2021
We are adding two new endpoints for working with Meetings.
/meetings/controls.Meeting Participants allows you to retrieve and update participant information for live or finished meetings. This endpoint also supports the previously introduced functionality allowing applications to act on behalf of another user in the organization. Meetings Controls allows applications to see and update meeting features like the
January 6, 2021
Coming Feb 15, 2021, we will no longer allow file attachments via urls in the messages files field. Instead, use multipart/form-data to attach files directly into the message. Examples for multipart/form-data upload can be found here
December 8, 2020
We now provide the ability for org admins to work with the meetings endpoint on behalf of another user via the new hostEmail field. This opens up a whole new set of capabilities where an authorized app may act on behalf of any user in the org to schedule, read, update meetings. Please see the meetings endpoint for the 2 new fields hostEmail and siteUrl and the Admin section in the meetings REST API guide
December 8, 2020
We now provide the ability for org admins to work with the recordings endpoint on behalf of another user via the new hostEmail field. This opens up a whole new set of capabilities where an authorized app may act on behalf of any user in the org to retrieve meeting recordings. Please see the recordings endpoint for the 2 new fields hostEmail and siteUrl and the Admin section in the meetings REST API guide
December 4, 2020
We do provide now the ability for org admins to query meeting-qualities-data for experience and quality analysis in orgs with ProPack subscription. The data is similar to what admins can see today in the analysis report, but is provided in raw form for analysis by 3rd party systems. Please see here
November 12, 2020
We are providing the ability to set and retrieve Space Classifications via the API. Space Classifications need to be configured by an admin in Control Hub and will be available to users to apply to spaces/rooms. Unclassified spaces default to public. Rooms resources classified higher than public will have a classificationId which can be compared to the results of the new /classifications API. Events are available as room update events. Don't forget a classification can only be up classified (e.g. confidential -> highly confidential) and never down classified in either the API or the client.
November 10, 2020
The List Teams API will soon enforce a maximum value for the max query parameter. Currently, requests made for more than 1000 events will return a varying number of results. After December 1, 2020, requesting more than 1000 people will return an HTTP 400 error.
November 9, 2020
To increase performance and safety of our and our customers systems, we will restrict file uploads via the messages API by Dec 1, ’20. As a first step files of the following mime types will not be fetched for upload anymore: application/octet-stream, application/x-zip-compressed, application/x-msdownload, application/x-apple-diskimage Mime types must be provided to being able to filter according to these restrictions. Files, where the server doesn't return a MIME or Content-type will be rejected. In addition by Jan 31, ’21 we will not allow file attachments via the messages files field any longer. Instead customers are required to use multipart/form-data to attach files directly into the message. Examples for the multipart/form-data upload can be found here
October 21, 2020
The List People API will soon enforce a maximum value for the max query parameter. Currently, requests made for more than 1000 events will return a varying number of results. After November 10, 2020, requesting more than 1000 people will return an HTTP 400 error.
October 13, 2020
The new Workspaces API will replace the Places API, which will be deprecated on March 31, 2021. In addition to what the Places API provided, the new Workspaces API allows developers to assign a type and a capacity for a workspace. For more information on workspaces, see the blog post Workspaces in Control Hub— What’s in it for you?.
October 5, 2020
We are going to make changes to the file uploads via the /messages files attribute. File uploads, not using the multipart/form-data content type, must be specified with the correct file extensions. For example .jpg .doc etc. Files types will be cross checked against an allow list and we may refuse upload of certain file types with a 422 error. For the list of allowed file types please check the /messages API reference.
September 29, 2020
Users who interact with buttons and cards in a Space Widget will now see the buttons and cards rendered in the widget as well. Developers who write apps that send cards can now use the data URI to embed images directly into the body of the message request instead of specifying html url references.
September 14, 2020
Admin users have the capability to filter the /people endpoint using the orgId to get a list of all users. The list response contains the user status for each person in the list. As a performance improvement, this user status will be removed from the default response. The info can be retrieved by using the query filter showAllTypes=true if the person's status information is required. Queries executed for specific users and queries done by regular users will not experience any change.
September 11, 2020
We may return a new status code 428 when trying to download files for users with Extended Security Pack when the files cannot be scanned for malware. The 428 code indicates that the file is unscannable, which is often true for encrypted files. API users will be able to force a file download with the parameter allow=unscannable.
September 11, 2020
We are making changes to the markdown rendering mechanism for improved performance and extensibility. While we have tested the most common scenarios users may experience differences in how their markup is shown in spaces after the rollout. If you experience such issues, please contact support at firstname.lastname@example.org or join the #webex4devs space for support.
September 10, 2020
Our initial release of the RESTful meetings APIs were focused primarily on scheduling, and the List Meetings API responded only with scheduled meetings objects, or meetings that have a
scheduledMeeting. Theses APIs will now also return meeting objects that have a
meeting, which represents an instance of a meeting that is happening or has happened in the past. When using the
statequery parameter on the List Meetings API, you may now use the states
expiredin addition to the previously working values
This will allow developers to create apps that discover meetings that have happened, meetings that have been missed, etc.
The /recordings will now accept a
meetingIdas a search parameter allowing developers to access the recording for a meeting that has ended.
September 10, 2020
We introduced a new message updated event, covering when a message in a space is edited. Previously, message edits showed as message creation events with an updated timestamp field. To make it easier for developers and CASB vendors to identify messages updated, the right event type - "updated" - is now used. Previous message edits will not be reclassified, i.e. the "updated" field will be present for messages from September 10th forward.
August 10, 2020
Memberships now includes a
roomTyperesponse property, which specifies the type of space (direct 1:1 or group) the membership is associated with.
August 10, 2020
You can now update the visibility of direct 1:1 spaces in the Webex Teams clients via the API. Memberships now includes the
isRoomHiddenparameter to specify whether a 1:1 space is hidden or visible in the clients. To change the visibility of a 1:1 space, use the Update a Membership endpoint. Compliance officers can update the visibility of memberships for any user in an organization.
August 4, 2020
The List Events API will soon enforce a maximum value for the
maxquery parameter. Currently, requests made for more than 1000 events will return a varying number of results. After August 17, 2020, requesting more than 1000 events will return an HTTP 400 error.
August 4, 2020
The List Rooms API will soon enforce a maximum value for the
maxquery parameter. Currently, requests made for more than 1000 rooms (spaces) will return a varying number of results. After September 4, 2020, requesting more than 1000 rooms will return an HTTP 400 error.
June 16, 2020
June 12, 2020
The Licenses API now provides more information about Webex Meetings licenses, including the site URL, subscription ID, and site link status.
May 28, 2020
You can now manage Webex Meetings with the new Webex Meetings REST APIs. With the new APIs, you can view, schedule, and manage Meetings, manage Meeting Invitees, retrieve or delete Recordings, and view or configure Meeting Preferences. Learn more about the new APIs in our blog: Introducing the new Webex Meetings REST APIs.
May 20, 2020
Buttons and Cards now support Adaptive Cards 1.2 features. The Messages API will also now validate card syntax before sending new messages. There's also a new, interactive Buttons and Cards Designer to design and create cards. Learn more about the changes in our blog: Buttons and Cards now support Adaptive Cards 1.2.
May 12, 2020
The Webex REST API has a new host name: webexapis.com. The new host name works just like the old one. All API resources and endpoints from api.ciscospark.com are now available at the new host name. Read more about the change in our blog: Introducing the new webexapis.com.
February 14, 2020
October 21, 2019
October 21, 2019
July 19, 2019
sipAddressproperty currently returned via the Get Room Details endpoint is now deprecated. After September 30, 2019, this property will no longer return the SIP address for the space. Instead, use the Get Room Meeting Details endpoint to retrieve the space's SIP address along with more detailed meeting information such as PSTN numbers and the meeting URL.
June 13, 2019
You can now retrieve extended meeting details for a space (room). Use the new Get Room Meeting Details action to see the meeting details for the space such as the SIP address, Webex Meetings URL, and PSTN dial-in numbers.
May 2, 2019
April 11, 2019
Memberships will soon include two new response properties:
roomType, which will specify the type of space (direct 1:1 or group) the membership is associated with, and
isRoomHidden, which will specify whether or not a 1:1 space is hidden in the Webex Teams clients for the participant.
March 15, 2019
Beginning April 27, 2019, the Webex platform will require that API clients use the Transport Layer Security (TLS) 1.2 protocol. To align with industry best practices for transport security, the TLS 1.1 encryption protocol will be disabled on all endpoints. See this blog post for more information.
January 30, 2019
The People API now includes a
phoneNumbersresponse property, which will provide the phone numbers associated with the person. This read-only property will only be returned for people within the same organization.
December 20, 2018
Currently, compliance officers can only see membership Events for spaces owned by their organization. Soon, compliance officers will have access to membership events for all spaces which include members of their organization, regardless of the space's owner.
December 19, 2018
Compliance officers can now delete messages in 1:1 spaces that were sent by an external user. Previously, messages in 1:1 spaces from an external user could only be monitored.
December 18, 2018
You can now retrieve messages in a 1:1 space without first knowing the
roomIdof the conversation. Use the new List Direct Messages action with the other party's person ID or email to retrieve messages from the 1:1 space.
September 18, 2018
A new type of application is now available! Guest Issuer apps may now be created to let guest users collaborate with your organization’s paid users. See our Guest Issuer documentation for more information about Guest Issuer apps.
September 6, 2018
The Memberships API will no longer return memberships and will instead return a 404 Not Found for team spaces (rooms) which are archived.
August 30, 2018
The People API will soon include a new
phoneNumbersfield, which will provide the phone numbers associated with the person. This read-only field will be returned for people within the same organization.
July 31, 2018
July 31, 2018
July 20, 2018
The Messages API will soon accept group mentions, such as @all, when creating new messages. Check back for more information within the coming weeks.
June 15, 2018
June 15, 2018
The Messages API currently accepts values for both the
markdownparameters when sending a message. After July 15, 2018, this API will return an error if a new message contains values for both parameters. Use only one parameter for the message body. Markdown content will be automatically transformed to plain-text for API clients which support only plain-text messages.
June 15, 2018
The following scopes have been deprecated and will no longer work after August 15, 2018:
spark-admin:team_memberships_write. They are no longer available for testing via Test Mode in the Webex Teams API Reference, or with your portal token, if you are an Organization Administrator. These scopes have been replaced by
spark-compliancescopes for use by designated Compliance Officers. See this guide for more information about compliance scopes.
April 16, 2018
The Messages API currently accepts @mentions in 1:1 messages. After May 26, 2018, this API will return an error if a message sent to a 1:1 space contains an @mention.
April 10, 2018
All licenses for Hybrid Services which are available for an organization, both enabled and disabled, will now be returned via the Licenses API. Hybrid Services licenses may now be assigned to users before a particular service is activated.
February 8, 2018
Beginning March 17, 2018, the Cisco Spark platform will require API clients to use TLS 1.1 or higher. The TLS 1.0 encryption protocol will be disabled on all endpoints to align with industry best practices for transport security. See this blog post for more information.