WHOOP Python API Docs | dltHub
Build a WHOOP-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
WHOOP API documentation includes endpoints for recovery data, sleep, and workouts; v1 webhooks have been removed, and v2 API is now available; terms of use cover liability for API use. The REST API base URL is https://api.prod.whoop.com and All requests require OAuth2 (Authorization Code) and a Bearer access token..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading WHOOP data in under 10 minutes.
What data can I load from WHOOP?
Here are some of the endpoints you can load from WHOOP:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| user_body_measurements | /v2/user/measurement/body | GET | Get user body measurements (height_meter, weight_kilogram, max_heart_rate) | |
| user_profile_basic | /v2/user/profile/basic | GET | Get basic user profile (user_id, email, first_name, last_name) | |
| activity_sleep_collection | /v2/activity/sleep | GET | Get collection of sleeps (paginated; params: start,end,limit,nextToken) | |
| activity_sleep_by_id | /v2/activity/sleep/{sleepId} | GET | Get single sleep by id | |
| activity_workout_collection | /v2/activity/workout | GET | Get collection of workouts (params: start,end,limit,nextToken) | |
| activity_workout_by_id | /v2/activity/workout/{workoutId} | GET | Get single workout by id | |
| cycle_collection | /v2/cycle | GET | Get cycles collection (params: start,end,limit,nextToken) | |
| cycle_by_id | /v2/cycle/{cycleId} | GET | Get single cycle by id | |
| cycle_sleep | /v2/cycle/{cycleId}/sleep | GET | Get sleep associated with a cycle | |
| recovery_collection | /v2/recovery | GET | Get recoveries collection (params: start,end,limit,nextToken) | |
| cycle_recovery | /v2/cycle/{cycleId}/recovery | GET | Get recovery for a cycle | |
| activity_id_mapping | /v2/activity/id_mapping | GET | Utility endpoint returning V2 UUID for V1 Activity ID | |
| revoke_oauth_access | /v2/user/access | DELETE | Revoke a user's OAuth access (204 no content) |
How do I authenticate with the WHOOP API?
WHOOP uses OAuth 2.0 (authorization code flow). Obtain client_id and client_secret from the developer dashboard, exchange an authorization code at https://api.prod.whoop.com/oauth/oauth2/token, and send the returned access_token as a Bearer token in the Authorization header.
1. Get your credentials
- Sign in to the WHOOP Developer Dashboard at https://developer-dashboard.whoop.com.
- Create a new App and configure at least one Redirect URI.
- In the App details copy the Client ID and Client Secret.
- Direct users (or yourself) to the authorization URL https://api.prod.whoop.com/oauth/oauth2/auth to obtain an authorization code.
- Exchange the authorization code at https://api.prod.whoop.com/oauth/oauth2/token to receive an access_token (and a refresh_token if the offline scope was requested). Include the access_token in the Authorization: Bearer header for subsequent API calls.
2. Add them to .dlt/secrets.toml
[sources.whoop_source] client_id = "your_client_id" client_secret = "your_client_secret" refresh_token = "optional_refresh_token_if_offline_scope_requested"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the WHOOP API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python whoop_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline whoop_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset whoop_data The duckdb destination used duckdb:/whoop.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline whoop_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads activity_sleep and activity_workout from the WHOOP API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def whoop_source(client_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.prod.whoop.com", "auth": { "type": "bearer", "access_token": client_secret, }, }, "resources": [ {"name": "activity_sleep", "endpoint": {"path": "v2/activity/sleep"}}, {"name": "activity_workout", "endpoint": {"path": "v2/activity/workout"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="whoop_pipeline", destination="duckdb", dataset_name="whoop_data", ) load_info = pipeline.run(whoop_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("whoop_pipeline").dataset() sessions_df = data.activity_sleep.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM whoop_data.activity_sleep LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("whoop_pipeline").dataset() data.activity_sleep.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load WHOOP data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for WHOOP?
Request dlt skills, commands, AGENT.md files, and AI-native context.