MyWhoop is a tool for gathering and retaining your Whoop data from the Whoop API.
MyWhoop is a tool intended to help you take ownership of your Whoop data. You can use MyWhoop to download all your Whoop data. You can also use MyWhoop as a server to automatically download your new Whoop data daily. MyWhoop is designed to be deployed on your own machine or server. MyWhoop supports the following features:
- 🔐 Login: A simple interface to log into the Whoop developer portal and save an authentication token locally. The token is required to interact with the Whoop API.
- 🗄️ Server: Automatically download your Whoop data daily and save it to a local file or export it to a remote location.
- 📬 Notifications: Receive notifications when new data is available or when an error occurs.
- 💾 Data Export: Export your Whoop data to a remote location like S3 bucket.
- 🗂️ Extensions: Data exporters and notification services can be extended to support additional use cases. Check out the Extensions section to learn more.
- 📦 No Dependencies: MyWhoop is available as a stand-alone binary or Docker image. No additional software is required to get started.
Please check out the Getting Started guide to get started with MyWhoop.
To set up MyWhoop in server mode, use the Setup Server Mode guide.
MyWhoop supports the following commands and global flags:
- Dump - Download your Whoop data and save it to a local file.
- Login - Authenticate with the Whoop API and save the authentication token locally.
- Help - Display help information for MyWhoop.
- Server - Automatically download your Whoop data daily and save it to a local file or export it to a remote location.
- Version - Display the version of MyWhoop.
| Long Flag | Short Flag | Description | Required | Default |
|---|---|---|---|---|
--config |
- | The file path to the MyWhoop configuration file. | No | ~/.mywhoop.yaml |
--credentials |
- | The file path to the Whoop credentials file that contains a valid Whoop authentication token. | No | token.json |
--debug |
-d |
Modify the output logging level. | No | INFO |
Important
For more information on the MyWhoop configuration file, refer to the Configuration Reference section.
The dump command downloads all your Whoop data and saves it to a local file. For more advanced configurations, use a Mywhoop configuration file. Refer to the Configuration Reference section for more information.
mywhoop dump| Long Flag | Short Flag | Description | Required | Default |
|---|---|---|---|---|
--location |
-l |
The location to save the Whoop data file. | No | ./data/ |
--filter |
-f |
Specify a filter string to filter the data. For example to download all the data from January 2024 start=2024-01-01T00:00:00.000Z&end=2024-01-31T00:00:00.000Z. You can learn more about the filter syntax in the Whoop API Pagination documentation. |
No | "" |
--output |
-o |
The output format. Supported types are json or xlsx. |
No | json |
You can filter the data using the --filter flag. The filter flag expects a string that follows the Whoop API Pagination filter syntax. A start value is required, the end value is optional. For example, to download all the data from January 2024, use the following filter string.
mywhoop dump --filter "start=2024-01-01T00:00:00.000Z&end=2024-01-31T00:00:00.000Z"Tip
Wrap the filter string in quotes to prevent the shell from interpreting the & character as a command separator.
You can omit the end value to download all the data from the specified start date to the current date. For example, use the following filter string to download all the data from March 2022 to the current date.
mywhoop dump --filter "start=2022-03-01T00:00:00.000Z"If you specify an invalid filter string, Whoop will normaly ignore the filter and return all the data.
Important
MyWhoop has exponential backoff and retries logic built in for the Whoop API. If the API is down or the request fails, MyWhoop will retry the request. Whoop has an API rate limit of 100 requests per minute. If the rate limit is exceeded, MyWhoop will attempt to retry the request after a delay for up to a maximum of 5 minutes. If the request fails after 5 minutes, the application will exit with an error. If the Whoop API rejects the authentication token, the application will exit with an error.
The login command is used to authenticate with the Whoop API and save the authentication token locally. The command will set up a local static HTTP server hosting a simple website to handle the OAuth2 handshake with the Whoop API and save the token to a local file.
mywhoop login| Long Flag | Short Flag | Description | Required | Default |
|---|---|---|---|---|
--no-auto-open |
-n |
By default, the login command will automatically open a browser window to the Whoop login page. Use this flag to disable this behavior. | No | False |
--port |
-p |
The port to use for the local HTTP server. | No | 8080 |
--redirect-url |
-r |
The redirect URL to use for the OAuth2 handshake. | No | http://localhost:8080/redirect. |
The server command automatically downloads your Whoop data daily. If specified through a configuration file, the server saves or exports the data to a local file or a remote location. The server is designed to be started as a background process and will automatically download your Whoop data daily. The command will refresh the Whoop authentication token every 45 minutes and update the local token file. The Whoop API is queried precisely every 24 hours from when the server is started.
Important
A Whoop authentication token is required to use the server command. The server will attempt to refresh the token immediately upon to startup. If the token is invalid or expired, the server will exit with an error. Use the login command to authenticate with the Whoop API and save the token locally. The reason for the immediate refresh is to support use cases where the server is started and stopped, such as system reboots or server restarts.
mywhoop serverUse a MyWhoop configuration file for more advanced configurations. For more information, refer to the Configuration Reference section.
mywhoop server --config /opt/mywhoop/config.yamlThe version command is used to display the version of MyWhoop. The version command checks for the latest version of MyWhoop and displays the current version. If a new version is available, the command will notify you.
mywhoop version2024/07/06 10:50:29 INFO mywhoop v0.1.0
MyWhoop supports extensions for data exporters and notification services. Exporters are used to export your Whoop data to a remote location, such as an S3 bucket or to a unique data store. Notification services are used to send notifications when new data is available or when an error occurs. Extensions are configured in the MyWhoop configuration file. For more information, refer to the Configuration Reference section.
| Name | Description | Configuration |
|---|---|---|
| File | This is the default exporter. The exporter saves the Whoop data to a local file. | File Exporter |
| AWS S3 | The AWS S3 exporter saves the Whoop data to an S3 bucket. | AWS S3 Exporter |
| Name | Description | Configuration |
|---|---|---|
| stdout | The stdout notification is the default notification mechanism. Output is sent to the console. | Stdout |
| Ntfy | Use the Ntfy notification service to send notifications to your phone or desktop. | Ntfy |