Cisco Spaces SDK Methods

Initialization

• registerSdk

User identity association and management

Note: There are three options for associating a user to the device (registering user at Cisco Spaces Backend). These options are based on polymorphism, that is they use the same method name. The correct one of the three methods listed below is executed based on the parameters provided during the method's invocation:

• Option  1 - Server Auth Code based: User must be authenticated before being associated to the device. The authentication should be handled by the application before calling the method. In this option, the method expects to receive the Server Auth Code from the application.

• Option 2 - Webview based: User must be authenticated before being associated to the device. The SDK method will provide the authentication URL to be rendered in a webview provided by the application. If the authentication is successful, the user is associated to the device at Cisco Spaces Backend.

• Option  3 - User ID based: No authentication is required in this case. The user will be identified by an ID informed by the application through this method option.

• associateUser (Server Auth Code based)

• associateUser (Webview based)

• associateUser (User ID based)

• updateUserDetails

• getUserDetails

• deleteUserAccount

• getPrivacySettings

• setPrivacySettings

User profile management

• installProfile
• profileExistence
• deleteProfile

Push

• associatePushIdentifier
• dissociatePushIdentifier
• handleNotification

Note : Android Push Notification API is deprecated as on 20thJune2024. Work in progress on the new FCM changes suggested by Google.

Usage Statistics

• getUsageStatistics

Location information

• getLocation
• getLocationDetails

User Tags

• setUserTags
• deleteUserTags