Skip to main content

Support

FAQ​

How do I get started with the WHOOP Developer Platform?​

To get started, you need to sign up for an account on whoop.com and obtain a WHOOP device. Once you have an account, you can create an application by navigating to Dashboard on developer.whoop.com and logging in with your account credentials. You can reference our getting started guide to learn how to integrate WHOOP data into your application.

What data is available through the WHOOP API?​

The WHOOP API provides access to various types of data, including activity data, sleep data, recovery data, and more. For a detailed list of available endpoints and the data they return, please refer to our API documentation.

Are there any costs associated with using the WHOOP API?​

Access to the WHOOP Developer Platform and API is currently free. However, you must have a WHOOP device, which requires a membership. Check join.whoop.com for more details.

Do you offer a sandbox environment for developers who do not have a WHOOP?​

We require all developers on the Developer Platform to have a WHOOP device. Using WHOOP and understanding the user flow dramatically helps with understanding and integrating with our API.

What are the future improvement plans for the WHOOP API?​

We strive to continuously improve our API offering and make it straightforward to work with. We will regularly update the API as new functionality and features are released, and note the update in our changelog. For ideas on enhancing the API, please share them with us.

What is your rate limiting policy?​

Check out our rate limiting policy here.

What is a rough estimate of how much a day’s worth of data for an individual would be in terms of KB?​

A day’s worth of member data (with one workout, one sleep, and one recovery) would be about 4 KB. For each additional workout or nap, add 1 KB.

How often should we refresh tokens in the OAuth flow?​

You should refresh tokens every hour. See an example flow here and documentation for refreshing an access token here.

Do I, as the developer, need to show that my app has collected a member’s authorization in my UI?​

The WHOOP member should always be able to see that they've granted you access to their data. You should offer an easy and intuitive way for the member to disable the integration as well. The member can also revoke access to an integration via the WHOOP app.

Generally, what is the lift to use the API?​

The WHOOP API utilizes OAuth 2.0 authentication, which is well-documented and industry standard, and webhooks to notify when new data is available. Integrating with the WHOOP API is very straightforward. Typically, the hardest part of integrating with the WHOOP API is understanding the data model (e.g., what is a physiological cycle, and how does that differ from a calendar day?). We’ve heard from countless developers that wearing a WHOOP makes understanding the API and data model significantly easier.

Does the API offer access to continuous heart rate data?​

Each WHOOP device can broadcast heart rate over Bluetooth Low Energy (BLE) to other devices. Many applications have implemented a Bluetooth listener to let members connect their WHOOP as a heart rate monitor. Continuous heart rate data is not available via the WHOOP API.

Submitting feedback​

If you are encountering issues with or have feedback about the WHOOP API, you can submit a request. Please note that responses to this form may take some time.

Still have questions? Share your questions with us.