<![CDATA[Cisco Webex for Developers Changelog API]]> https://developer.webex.com/docs/api/api-changelog https://developer.webex.com/images/home-hero.svg Cisco Webex for Developers Changelog API https://developer.webex.com/docs/api/api-changelog RSS for Node Thu, 19 Sep 2019 02:44:49 GMT <![CDATA[Buttons and Cards GA Release]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2019-august blt4ea84670a3b0ec5b Tue, 06 Aug 2019 00:00:00 GMT
<![CDATA[Rooms sipAddress Deprecation Notice]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2019-july blt33237f52b778d730 Fri, 19 Jul 2019 00:00:00 GMT
<![CDATA[New Rooms meetingInfo action]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2019-june bltf0c8959a4f03d97c Thu, 13 Jun 2019 00:00:00 GMT
<![CDATA[Additional People Status Values]]> People now includes additional status values: "call", "meeting", and "presenting". See this article for more information about the different status options in Webex Teams.

]]>
https://developer.webex.com/docs/api/changelog/2019-may blt4640ba8552009829 Thu, 02 May 2019 00:00:00 GMT
<![CDATA[New People Response Property]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2019-may bltff599617d516e5c3 Wed, 01 May 2019 00:00:00 GMT
<![CDATA[New Memberships Response Properties]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2019-april blt152f492abe325c85 Thu, 11 Apr 2019 00:00:00 GMT
<![CDATA[TLS 1.2 Requirement]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2019-march blte80b1024cf59784d Fri, 15 Mar 2019 00:00:00 GMT
<![CDATA[phoneNumbers property GA]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2019-january blte0bf412ac1b361c1 Wed, 30 Jan 2019 00:00:00 GMT
<![CDATA[Memberships events for participating organizations]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-december bltb8443ffd30da6a0d Thu, 20 Dec 2018 00:00:00 GMT
<![CDATA[Compliance offices can now delete participating messages]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-december bltea3f21690a730c19 Wed, 19 Dec 2018 00:00:00 GMT
<![CDATA[List Direct Messages API GA]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-december blt2e75410823a7315e Tue, 18 Dec 2018 00:00:00 GMT
<![CDATA[Guest Issuer GA]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-september blt0a1ce9102d327486 Tue, 18 Sep 2018 00:00:00 GMT
<![CDATA[Memberships for archived team spaces]]> The Memberships API will no longer return memberships and will instead return a 404 Not Found for team spaces (rooms) which are archived.

]]>
https://developer.webex.com/docs/api/changelog/2018-september blt4c86e0dc7291baff Thu, 06 Sep 2018 00:00:00 GMT
<![CDATA[Resource Groups and Resource Group Memberships API GA]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-september blte51d919b33124e11 Wed, 05 Sep 2018 00:00:00 GMT
<![CDATA[Announcement: phoneNumbers field coming to People]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-august blta858a2c52c8a641c Thu, 30 Aug 2018 00:00:00 GMT
<![CDATA[Fetching messages with group mentions]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-july blt359deae2d527d877 Tue, 31 Jul 2018 00:00:00 GMT
<![CDATA[Sending messages with group mentions]]> The Messages API now accepts group mentions, such as @all, when creating new messages. See the Formatting Messages guide for details.

]]>
https://developer.webex.com/docs/api/changelog/2018-july bltdbba530c885d8992 Tue, 31 Jul 2018 00:00:00 GMT
<![CDATA[Announcement: Sending messages with group mentions]]> The Messages API will soon accept group mentions, such as @all, when creating new messages. Check back for more information within the coming weeks.

]]>
https://developer.webex.com/docs/api/changelog/2018-july blt81e08cb35f304346 Fri, 20 Jul 2018 00:00:00 GMT
<![CDATA[@mentions for nonexistent emails]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-july blt67949bb6e47484f3 Thu, 05 Jul 2018 00:00:00 GMT
<![CDATA[New Admin Roles]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-june blta1999bddfcd6e293 Fri, 15 Jun 2018 00:00:00 GMT
<![CDATA[Announcement: Messages dropping support for both text and markdown]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-june bltfb949c700607117e Fri, 15 Jun 2018 00:00:00 GMT
<![CDATA[Admin scope removal]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-june blt71baaf55516e161e Fri, 15 Jun 2018 00:00:00 GMT
<![CDATA[@mentions in 1:1 messages]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-april blt11956c7fb4b13102 Mon, 16 Apr 2018 00:00:00 GMT
<![CDATA[Hybrid Services License Change]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-april blt4a2648490d6c2572 Tue, 10 Apr 2018 00:00:00 GMT
<![CDATA[TLS 1.1 Requirement]]> 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.

]]>
https://developer.webex.com/docs/api/changelog/2018-february blt208e539e50a354a4 Thu, 08 Feb 2018 00:00:00 GMT