Android (Kotlin)
Current Android (Kotlin) SDK Version: 3.1.6
Android Package can be found here
Spike Android SDK is a library on top of Android HealthConnect that
- helps with the extraction of data.
- pushes data to SpikeAPI and delivers standardized data.
Do note, that according to Google's specification, you should only use SDK while the consuming app is in the foreground. Please make sure that you follow the advice shown here before releasing the app to production, especially the mandatory declaration.
- Android 9.0+
To add the SDK to your project, you have to add the following to your project's build.gradle file in the repositories block.
After that, add the following to your app's build.gradle file in the dependencies block.
Add the required health permissions to your android/app/src/main/res/values/config.xml. That allows you to fully utilize Spike SDK and to read the necessary data from apps that integrate with HealthConnect. Please refer to this guide to understand the specific permissions needed.
Add an intent filter to your activity definition so that you can request the permissions at runtime.
To handle Android 14 you also need to add activity-alias to your AndroidManifest.xml It is just a wrapper for the activity that requests permissions so no real activity is necessary.
Internally, the Android SDK supports logging on various levels to assist with troubleshooting. However, the SDK expects a concrete logging implementation to be provided externally to avoid imposing additional third-party dependencies on library users. This can be done by implementing the SpikeLogger class and providing it when creating or unpacking a connection.
Below is an example of how to implement a simple console logger.
The SpikeSDK for Android devices integrates with Health Connect for data retrieval. Before publishing the application to the Play Store, application owners are required to complete the Developer Declaration Form available at the following link: Developer Declaration Form
Please make sure that all types are selected from permissions section as shown here
The following table shows the data types that can be read from HealthConnect API and the permissions that are required to read them.
Spike Data Type | HealthConnect permission |
---|---|
SpikeDataTypes.HEART_RATE | android.permission.health.READ_HEART_RATE android.permission.health.READ_HEART_RATE_VARIABILITY android.permission.health.READ_RESTING_HEART_RATE |
SpikeDataTypes.DISTANCE | android.permission.health.READ_DISTANCE |
SpikeDataTypes.ACTIVITIES_STREAM | android.permission.health.READ_EXERCISE android.permission.health.READ_STEPS android.permission.health.READ_DISTANCE android.permission.health.READ_TOTAL_CALORIES_BURNED android.permission.health.READ_HEART_RATE android.permission.health.READ_SPEED android.permission.health.READ_ELEVATION_GAINED android.permission.health.READ_POWER android.permission.health.READ_HEART_RATE_VARIABILITY |
SpikeDataTypes.ACTIVITIES_SUMMARY | android.permission.health.READ_STEPS android.permission.health.READ_ACTIVE_CALORIES_BURNED android.permission.health.READ_TOTAL_CALORIES_BURNED android.permission.health.READ_DISTANCE android.permission.health.READ_ELEVATION_GAINED android.permission.health.READ_FLOORS_CLIMBED android.permission.health.READ_HEART_RATE android.permission.health.READ_RESTING_HEART_RATE android.permission.health.READ_BASAL_METABOLIC_RATE |
SpikeDataTypes.BREATHING | android.permission.health.READ_RESPIRATORY_RATE |
SpikeDataTypes.CALORIES | android.permission.health.READ_TOTAL_CALORIES_BURNED android.permission.health.READ_ACTIVE_CALORIES_BURNED |
SpikeDataTypes.GLUCOSE | android.permission.health.READ_BLOOD_GLUCOSE |
SpikeDataTypes.OXYGEN_SATURATION | android.permission.health.READ_OXYGEN_SATURATION |
SpikeDataTypes.SLEEP | android.permission.health.READ_SLEEP android.permission.health.READ_HEART_RATE android.permission.health.READ_HEART_RATE_VARIABILITY |
SpikeDataTypes.STEPS | android.permission.health.READ_STEPS |
SpikeDataTypes.BODY | android.permission.health.READ_WEIGHT android.permission.health.READ_HEIGHT android.permission.health.READ_BODY_FAT android.permission.health.READ_BONE_MASS android.permission.health.READ_BLOOD_PRESSURE android.permission.health.READ_BODY_TEMPERATURE |
Class | Method | Description |
---|---|---|
SpikeConnection | createConnection | Creates a new SpikeConnection instance with the given user details. Parameters: appId, authToken, customerEndUserId, logger Returns: An instance of the SpikeConnection class. |
SpikeConnection | hasHealthPermissionsGranted | Initiates a check on whether all health permissions have been granted to ensure the proper functioning of the SDK Returns: True / False |
SpikeConnection | getAppId | Retrieves the unique Spike application identifier. Returns: string |
SpikeConnection | getSpikeEndUserId | Retrieves the unique identifier assigned to the end-user by Spike. Returns: string |
SpikeConnection | getCustomerUserId | Retrieves the unique identifier assigned to the end-user by the customer. Returns: string |
SpikeConnection | close | Terminates any ongoing connections with Spike’s backend servers, clears any caches, and removes provided user details and tokens from the memory. Once the connection is closed, it cannot be used, and any method other than close() will throw a SpikeConnectionIsClosed exception. |
SpikeConnection | extractData | Extracts local device data for the current date in the end-user’s time zone. Optionally time range can be provided. *On iOS, the maximum allowed single-query time interval is 90 days. If required, data of any longer time period can be accessed by iterating multiple queries of 90 days. *On Android the earliest date data can be requested for 30 days before permission was given to the user's app to read from HealthConnect. There is no limit on how many days in total. Parameters: dataType, from, to Returns: An instance of SpikeData. The concrete type will depend on the data type requested |
SpikeConnection | extractAndPostData | Extracts local device data for the current date in the local user time zone and sends it as a webhook notification to the customer’s backend. Optionally time range can be provided. *On iOS, the maximum allowed single-query time interval is 90 days. If required, data of any longer time period can be accessed by iterating multiple queries of 90 days. *On Android the earliest date data can be requested is 30 days before permission was given to the user's app to read from HealthConnect. There is no limit on how many days in total. Parameters: dataType, from, to |
SpikeConnection | manageHealthConnect | Opens your device's HealthConnect menu, where you can switch on and off data access for the app as well as delete data. |
SpikeConnection | getHealthConnectAvailability | Provides information on whether HealthConnect is available on the device. |
SpikeConnection | revokeAllPermissions | Revokes all granted health permissions for the application. |
SpikeConnection | | |
SpikeConnection | | |
The abstract parent of all concrete exceptions.
Thrown if any method is invoked on SpikeConnection or one of its subclasses after the connection has been closed.
Thrown if the credentials provided are not recognised, i.e. are invalid or expired.
Thrown if duration exceeds the allowed maximum or if ‘from’ date is greater than ‘to’ date. The message will contain a specific cause description.
Thrown if the callback URL is not a valid URL, does not have HTTPS schema, or is not a sub-URL of the main callback URL configured for the application. The exception message will contain a specific reason.
Thrown when Spike SDK is unable to access the data due to permissions not being granted.
Whenever any operation with the Spike backend fails and the error does not fall into any of the above exceptions. The exception cause will contain the underlying error.
Thrown when a connection cannot be deserialised from a packed state. The exception cause will contain the underlying error.
An exception can be thrown from HealthConnect Client itself and due to its nature has to be caught on the app side and cannot be wrapped on SDK side.
Thrown when data is requested too often on HealthConnect API. Can also be thrown when there is an internal error in HealthConnect API communication.