FAQ

After clicking the "Connect X device" button, the user will be directed to the website of the data provider, where they will need to confirm permission to use their data. Once confirmed, the user will be redirected back to the app or website. It's possible to configure the postback option through the developer console.

The resources required to integrate with Spike API will depend on a few factors, such as the complexity of your application, your team's familiarity with API integrations, and the specific features of the Spike API that you plan to use.

In general, you will need to allocate some time and engineering resources to:

The amount of time and resources required for each step will depend on your specific situation. For example, if you have a team of experienced developers who have worked with APIs before, the integration process may be faster and require fewer resources. On the other hand, if you have a complex application and require a lot of customization, the integration process may take longer and require more engineering resources.

To get a better idea of the resources required for your specific integration, it's best to discuss your requirements with the Spike API team.

If you need to start testing Spike API, we recommend filling out the Contact Us form on our website.

The time it takes to go to production with an integration of Spike API will depend on a few factors, such as the complexity of your application, the specific Spike API features you plan to use, and your team's experience with API integrations.

Generally speaking, the integration process can take anywhere from a few days to several weeks or months.

To get a more accurate estimate of the time it will take to go to production with your integration, it's best to work closely with the Spike API team.

Yes, for Polar devices.

When we say that data is "standardized," we mean that it has been transformed or processed in a way that makes it consistent, structured, and ready for analysis or use in the applications.

Standardization typically involves the application of a set of rules that define how data should be formatted, organized, and represented. These rules can vary depending on the type of data.

Our machine learning (ML) service simplifies and accelerates the process of generating scores and predictions using data from wearable devices.

To backfill metrics for users you can use this metrics endpoint to request data for specific inclusive range of days:

../metrics/{metric}?user_id={user-id}&start_date={start-date}&end_date={end-date}

The start-date and end date should have a maximum difference of 7 days, allowing for the retrieval of a week's worth of data in a single request.

For example these four request would fetch sleep data for user X for 2023-04-01 - 2023-04-28 dates:

/metrics/sleep?user_id=X&start_date=2023-04-01&end_date=2023-04-07

/metrics/sleep?user_id=X&start_date=2023-04-08&end_date=2023-04-14

/metrics/sleep?user_id=X&start_date=2023-04-15&end_date=2023-04-21

/metrics/sleep?user_id=X&start_date=2023-04-22&end_date=2023-04-28

Fitbit, Oura, Google Fit and Withings have no restrictions on backfilling data whereas Garmin only allows data to be backfilled upto 14 days. Whoop does not allow backfilling data.

The frequency at which you can receive data from health and fitness tracking providers can vary depending on the specific platform and integration method you are using.

If you are using webhooks, data is typically delivered a few times per day. This means that you will receive updates and notifications periodically throughout the day, but not necessarily in real-time or at specific intervals like every 5 minutes or hourly.

Additionally, some providers may have rate limits on their pull data services. For example, Fitbit has a limit of 150 requests per hour per user.

It's important to note that the exact data delivery frequency and rate limits can vary depending on the provider and the specific integration setup. It's recommended to refer to the documentation or contact the provider directly to get precise information on data delivery intervals and any limitations that may apply.

Yes, please contact us at [email protected] and we will provide you sample data.

Yes, it is possible for apps developed on no-code platforms to integrate with the Spike API, as long as the app does not require connectivity to Apple Health or Android Health data.

Please contact us, it is very likely we are already developing this integration.

No, but we can help to develop it.

Yes, our infrastructure is highly scalable and capable of supporting large numbers of users connecting through the Spike API.

You must specify the User-Agent attribute on your web view component. You can find the example here: https://docs.spikeapi.com/add-user-integration#tJSoe

Yes, we understand the importance of maintaining your brand identity throughout the user experience. As part of our whitelabelling service, we offer the option to customize the authentication process to showcase your company's icon and name. By registering your company with our integration providers, we can ensure that your clients will see your branding consistently during the authentication flow. This customization allows for a seamless and personalized experience, reinforcing your brand's presence and trust with your clients. If you're interested in discussing the customization options for your application integration, please contact our support team, and we'll be happy to guide you through the process. *Dexcom, Google Fit and Huawei requires account to be created by the client in to order to ensure consistency across all boards

Yes, please note that we are using Retrofit library which requires additional configuration from your end on ProGuard. Please find more details here: https://github.com/square/retrofit?tab=readme-ov-file#r8--proguard