Update: This change will now be implemented beginning March 17, 2018 03:30 UTC. The Cisco Spark platform will require API clients to use TLS 1.1 or higher beginning March 17, 2018 UTC. The TLS 1.0 encryption protocol will be disabled on all endpoints to align with industry best practices for transport security. Additionally, the Cisco Spark API will require the use of clients which support the Server Name Indication (SNI) extension to TLS/SSL. Our internal telemetry of API connections indicates that very few apps are using TLS 1.0. To prevent any service disruption after March 2 between your apps and Cisco Spark, ensure that your app’s server operating system, libraries, and frameworks support at least TLS 1.1 and the SNI extension. Consult the documentation for your app’s libraries and frameworks to ensure that they support TLS 1.1. The following minimum versions of common libraries and tools support the SNI extension: Java 1.7 PHP 5.3 Python 2.7.9, Python 3 Ruby (net/http) 2.0 cURL 7.18.1 wget 1.14 If you have any questions about this change, our Cisco Spark DevSupport Team is available 24/7 to help. Please contact them with your question or concern. — Brian Bender, Technical Leader ... View more

We’ve been hard at work developing brand new ways to use our SDKs and Widgets in your Cisco Spark applications. This month, we’re releasing new versions of our iOS SDK, Browser SDK, and Widgets. Each one of them is jam-packed with new features and benefits. Let’s take a look! Cisco Spark iOS SDK Updates In addition to the current calling features, you can now use the Cisco Spark iOS SDK to participate in multi-party, group space calls and see shared presentation content. We’ve also developed another example app to demonstrate how you can harness the power of the Cisco Spark platform in your apps. Additional details include: iOS 11 support: Develop for the latest iOS release from Apple. Group space calling: Start or join meetings in group spaces right from within the SDK. Receive notifications for new meetings and join them easily. View shared content: Now, shared meeting content, such as presentations, can be viewed. Also, you’ll be able to view shared content and video from Cisco Spark meeting participants simultaneously. Buddies sample application: See a real-world example of using Cisco Spark messaging and meeting features in a brand new demo app, Buddies. Browser SDK Updates The Cisco Spark Browser SDK already lets you make and take calls with your Cisco Spark contacts, but now you can call anyone with an SIP address. On top of that, you can also participate in multi-party, group space calls. Here’s what else is new: Group space calling: Start or join meetings in group spaces right from within a browser. SIP and DTMF support: Call anyone with a SIP address. Plus, if you find yourself in an IVR menu, you can now use DTMF to navigate your way through it. Bandwidth controls: Limit the amount of bandwidth used by the SDK for calling features. A Widening Array of Cisco Spark Widget Features Utilizing Cisco Spark Widgets, you can already easily add messaging and meeting features into your web apps. Now, our widgets are getting some new features to make them even more powerful, including: Group space messaging: Say goodbye to being limited to just 1:1 chats. With our new Cisco Spark Space Widget, now users can join group spaces, chat with multiple people, and even @mention them. Manage people in group spaces: Users can now see who’s in a group space and add/remove people from spaces. Group space calling: Users can also now start or join meetings in group spaces right from within the Space Widget. SIP calling: The Cisco Spark Space Widget can now place calls directly to SIP endpoints. So What’s Up Next? Stay tuned, because we’ll soon be releasing a public beta of the Cisco Spark Android SDK. Be sure to watch the blog for updates or check out the Android SDK in early December. In the meantime, get started with these great new SDK features in your applications today! - Brian Bender, Technical Leader ... View more

The new Pro Pack for Cisco Spark™ Control Hub released this week provides you with advanced security, compliance, and analytics functionality right in the Cisco Spark Control Hub. Along with this release, a new Events API has been added to give developers access to events happening with their Cisco Spark organization. You can use the Events API to integrate with your existing Data Loss Prevention (DLP) software to check for policy violations and take action to resolve any issues. The events you can monitor include posting messages, sending content such as files, and adding users to spaces. You can also use the Events API to integrate with your existing archiving software to archive an unlimited amount of Cisco Spark data. For access to events older than 90 days, you will need the Pro Pack. The Events API provides access to activities within Cisco Spark after they have occurred. Perhaps you need to retrieve every message sent by a particular user to comply with a legal discovery process, or you need to know which rooms someone joined and left. The Events API will give you access to this information quickly and securely. The Events API is currently in Limited Availability. To gain access to the API, please submit a ticket to our Cisco Spark DevSupport team by emailing devsupport@ciscospark.com with your organization information. We focus on providing you the best features and experience. If you have any questions, feel free to reach out to us at devsupport@ciscospark.com or join the DevSupport Cisco Spark room. Follow us on Twitter to stay updated. - Brian Bender, Technical Leader ... View more

Recently we added a new integration scope called spark:all . The spark:all scope acts as an overall aggregate for the rest of the user scopes. It basically requests full access to a Spark account, i.e. reading/writing messages, creating/deleting spaces, making/receiving calls, and so on. From an integrations standpoint, this makes it really simple to communicate to a user that the app requires full access without needing to select individual user scopes (such as spark:messages_read , spark:messages_write , spark:people_read ). This is particularly useful for heavy-duty integrations, such as Cisco Spark calling apps. Prior to spark:all , individual user scopes were grouped and presented to the user for approval; with spark:all it requires approval for just one 'super' scope. When spark:all is selected, the rest of the user scopes will be disabled for selection: Even though spark:all acts as an aggregate scope, it is important to note that in the grant flow, the spark:all scope only aggregates user scopes – admin scopes are not part of spark:all and can be applied as add-ons, but no other user scope should be added when spark:all is selected. Users will be presented with the following screen in the grant flow when the integration requires spark:all : The spark:all scope is optional for the majority of the integrations. However, it is required for any app that uses calling features – you're effectively replicating a large portion (if not all) of a native Spark client at that point and need the complete set of scopes in order for your integration to function correctly. To learn more about integrations, please see the Authentication guide. We focus on providing you the best features and experience. If you have any questions, feel free to reach out to us at devsupport@ciscospark.com or join the DevSupport Spark room. Follow us on Twitter to stay updated. - Brian Bender, Technical Leader ... View more

Coming soon you'll be able to see SIP URIs for group Cisco Spark spaces! Now anyone can join a Cisco Spark meeting. All Cisco Spark spaces will have a SIP URI, allowing people to join meetings in those spaces from any standards-based SIP hardware or software client. The SIP URI will be returned for group spaces (not 1:1) via the Get Room Details API endpoint. We focus on providing you the best features and experience. If you have any questions, feel free to reach out to us at devsupport@ciscospark.com or join the DevSupport Spark space. Follow us on Twitter to stay updated! – Brian Bender, Technical Leader ... View more

Managing Cisco Spark Hybrid Services licenses is about to get easier with the Spark API. Organization Administrators will soon have the ability to list Hybrid Services licenses for an organization and use them to enable or disable services for users via the Spark API. The Licenses and People APIs make it easy to programmatically update people to add and remove various Spark licenses. With the addition of Hybrid Services licenses, administrators can quickly identify users who have these services enabled or disabled. License changes for a user can be made with a simple PUT request containing a list of licenses which should be enabled for the user. For more information about how to manage Hybrid Services licenses with users, see this guide in our developer documentation. We focus on providing you the best features and experience. If you have any questions, feel free to reach out to us at devsupport@ciscospark.com or join the DevSupport Spark space. Follow us on Twitter to stay updated. - Brian Bender, Technical Leader ... View more

Cisco Spark Organization Administrators will soon have access to two additional fields for People to determine a user’s provisioning status. When new users are invited to join Cisco Spark, an email is sent to them to continue the sign-up process. Now you will be able to determine via the People API if users have completed the sign-up process and if they are able to log into Spark. Two new Boolean-type fields will be returned for People to represent the user’s account provisioning status: Field Value Description invitePending true The user has been sent an invite, but has not completed the sign-up process invitePending false The user has been sent an invite, and has completed the sign-up process loginEnabled true The user is not allowed to log in loginEnabled false The user is allowed to log in These two additional read-only fields will be available when listing all People and when getting details for one person. This update will only add additional fields, and will not remove or rename any current fields. We focus on providing you the best features and experience. If you have any support questions, feel free to reach out to us at devsupport@ciscospark.com or join the DevSupport Spark space. Follow us on Twitter to stay updated. - Brian Bender, Technical Leader ... View more