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.

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.

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 devsupport@cisco.com or join the #webex4devs space for support.

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 meetingType of meetingSeries or scheduledMeeting. Theses APIs will now also return meeting objects that have a meetingType of meeting, which represents an instance of a meeting that is happening or has happened in the past. When using the state query parameter on the List Meetings API, you may now use the states inProgress, ended, missed, or expired in addition to the previously working values active, and scheduled.

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 meetingId as a search parameter allowing developers to access the recording for a meeting that has ended.

Administrators for organizations with Webex Calling can now set and get users location, phone number and extension via the /people API and the new /locations API. Learn more about the new Webex Calling Provisioning API please see the updated Webex Calling Guide.

Memberships now includes a roomType response property, which specifies the type of space (direct 1:1 or group) the membership is associated with.

You can now update the visibility of direct 1:1 spaces in the Webex Teams clients via the API. Memberships now includes the isRoomHidden parameter 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.

The List Events 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 August 17, 2020, requesting more than 1000 events will return an HTTP 400 error.

The List Rooms API will soon enforce a maximum value for the max query 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.

You can now use Webex Calling call control features with a new API: Call Controls. For more information about working with Webex Calling calls, see the Webex Calling Guide.

The Licenses API now provides more information about Webex Meetings licenses, including the site URL, subscription ID, and site link status.

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.

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.

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.

The Rooms API now includes an ownerId response property, which provides the ID of the organization which owns the room. For more information about room ownership, see Webex Teams Data in the Compliance Guide.

The Messages API now supports threaded message conversations in Webex Teams. Use the new parentId property when creating a message to create a new thread or to reply to an existing message thread. You can also use the new parentId query parameter to list messages in a particular thread.

Administrators for an organization can now use the new Hybrid Clusters and Hybrid Connectors resources to view details about their Cisco Webex Hybrid Services deployments via the Webex API.

Webex Devices and Places may now be managed via two new API endpoints: Devices and Places. For more information about working with devices and places, see the xAPI Guide.

You can now use the xAPI to programmatically invoke commands on and query the status of devices that run Webex RoomOS software. Check out the xAPI Guide and xAPI API Reference to get started.

Full administrators for an organization can now list Webex Control Hub Admin Audit Events. See this article for more information about the types of events that are available.

Your apps can now provide a web-like user interface with actionable buttons, input text boxes, dropdowns, checkboxes, images, and more right within Webex Teams spaces by including Cards when creating a message. Check out the announcement on the blog to learn more.

The sipAddress property 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.

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.

People now includes additional status values: "call", "meeting", and "presenting". See this article for more information about the different status options in Webex Teams.

People will soon include a new response property: lastModified, which will specify the date and time when the person was last modified, either directly via the API, Webex Control Hub, or the Cisco Directory Connector.

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.

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.

The People API now includes a phoneNumbers response 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.

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.

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.

You can now retrieve messages in a 1:1 space without first knowing the roomId of 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.

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.

The Memberships API will no longer return memberships and will instead return a 404 Not Found for team spaces (rooms) which are archived.

Webex Resource Groups for Hybrid Services may now be managed via two new API endpoints: Resource Groups and Resource Group Memberships. For more information about managing Resource Groups via the Webex API, see the Managing Hybrid Services guide.

The People API will soon include a new phoneNumbers field, which will provide the phone numbers associated with the person. This read-only field will be returned for people within the same organization.

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 now accepts group mentions, such as @all, when creating new messages. See the Formatting Messages guide for details.

The Messages API will soon accept group mentions, such as @all, when creating new messages. Check back for more information within the coming weeks.

The Messages API no longer rejects new messages which contain an @mention for an email address that is not associated with a Webex Teams user. The message will contain the display name, if provided, or the email address in plain text instead of the @mention.

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.

The Messages API currently accepts values for both the text and markdown parameters 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.

The following scopes have been deprecated and will no longer work after August 15, 2018: spark-admin:events_read, spark-admin:memberships_read, spark-admin:memberships_write, spark-admin:messages_read, spark-admin:messages_write, spark-admin:rooms_read, spark-admin:teams_read, spark-admin:team_memberships_read, and 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-compliance scopes for use by designated Compliance Officers. See this guide for more information about compliance scopes.

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.

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.