This page lists recent and upcoming changes to the Webex Teams API. Contact Webex Developer Support with any questions.
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.