This page lists recent and upcoming changes to the Webex Teams REST API. Contact Webex Developer Support with any questions.
- The Messages API now accepts group mentions, such as @all, when creating new messages. See the Formatting Messages guide for details.
- Group mentions in messages are now included in Messages API response details. A new response parameter,
mentionedGroups, will be present if a group is @mentioned in a message.
- The Messages API will soon accept group mentions, such as @all, when creating new messages. Check back for more information within the coming weeks.
- MAJOR 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.
- WARNING 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.
- Two new roles will soon be available via the Roles API: User Admin and Device Admin. These roles may be assigned or unassigned to users with the People API.
- WARNING 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.
- 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.
Last updated: November 8, 2018
- MAJOR 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.