Fitbit API
Integration
Connect Fitbit via OAuth 2.0 to sync workouts and activity data. Open Wearables handles the OAuth flow, polling, and normalization into one unified API.
Fitbit's Web API is being retired. In September 2026, Google will turn down the legacy Fitbit Web API, and it will stop syncing data entirely. New Fitbit developer accounts are no longer being issued, so this integration is already closed to new registrations.
Open Wearables is no longer developing the Fitbit integration. Workout and activity data sync continues to work until the shutdown date, but sleep, intraday heart rate, and daily activity summary, while available in the Fitbit Web API, will not be added.
If you need Fitbit users' data going forward, the recommended path is the Google Health API integration, which aggregates Fitbit data (along with Health Connect, Google Fit, and other sources) through Google's own account-level layer.
See the Google Health API integrationWhat you get from the Fitbit API.
Activity type and duration from the Fitbit app
Per activity
Per activity
Average heart rate during logged activities
Sleep, intraday heart rate, and daily activity summary are available in the Fitbit Web API but are not implemented in Open Wearables, and will not be added given the API's shutdown.
How Fitbit API integration works.
User connects their Fitbit account
Open Wearables handles the Fitbit OAuth 2.0 flow. Your users authorize access through Fitbit's standard consent screen.
Activity data syncs on a schedule
Open Wearables polls the Fitbit Web API for new workouts on a recurring schedule. Fitbit does not support webhooks for this data, so sync is pull-based only.
Your application calls one unified API
Fitbit activity data lands in the same schema as every other provider. No Fitbit-specific parsing logic in your codebase.
Fitbit is just the start.
One API, every provider. Plus health scores and AI reasoning.
All providers, one schema
Garmin, Whoop, Oura, Strava, Apple Health, Polar, Suunto, Samsung Health, Google Health Connect. Same endpoints, same data format.
See all providers →Open health scores
Sleep, recovery, strain, stress, HRV, VO2 max. Open algorithms you can audit and tune for your population.
Explore scores →AI reasoning engine
MCP server for any LLM. Detect trends, flag anomalies, build coaching profiles for wellness, performance, or clinical use cases.
Learn more →Open Wearables vs SaaS vs native Fitbit API.
| Aspect | Native Fitbit API | SaaS APIs | Open Wearables |
|---|---|---|---|
| OAuth implementation | You build and maintain it | Handled by provider | Handled by Open Wearables |
| Rate limit management | You track 150 req/hour per user | Handled by provider | Handled by Open Wearables |
| API sunset risk | You absorb the September 2026 shutdown yourself | Vendor absorbs it, opaquely | Documented, with a migration path to Google Health API |
| Data normalization | Fitbit-specific response format | Provider-defined schema | Unified schema across all providers |
| Multi-provider support | Separate integration per provider | Depends on vendor tier | One unified API for all providers |
| Per-user pricing | No platform fee | Charged per connected user | Self-hosted |
| Data ownership | You own all data | Vendor stores your users' data | You own all data |
← scroll to see all →
Why use Open Wearables for Fitbit API access.
Honest about the sunset
Open Wearables tells you upfront that Fitbit's Web API is going away, and gives you a working migration path instead of leaving you to find out from a broken integration in September 2026.
One less thing to rebuild twice
Connect through Open Wearables now, and switching a user from Fitbit to the Google Health API later does not mean rewriting your data layer. Same schema, same endpoints.
No dead-end OAuth flow to maintain
Open Wearables handles the Fitbit OAuth flow and rate limits (150 requests per hour) for the time the integration remains live, so you are not building infrastructure for an API that is shutting down.
Combine with other providers today
Pair existing Fitbit activity data with Garmin, Oura, or Whoop data in one query while you plan the migration.
Up and running in minutes.
GET /v1/events/workouts
{
"date": "2026-01-15",
"source": { "provider": "fitbit", "device": "Fitbit Charge 6" },
"type": "run",
"distance_m": 6200,
"duration_min": 32,
"heart_rate_avg_bpm": 151,
"calories_kcal": 412
}
Open Wearables is open-source and self-hosted. Fitbit developer registrations are closed, so this integration only applies if you already hold Fitbit API credentials. New integrations should start with the Google Health API instead.
Migrate off Fitbit before September 2026,
without rebuilding your data layer.
Open Wearables handles OAuth, rate limits, and normalization today, and gives you a direct path to the Google Health API when Fitbit shuts down. MIT licensed. Self-hosted.
Common questions.
Is Fitbit's API really shutting down?
Yes. Google has confirmed that the legacy Fitbit Web API will be turned down in September 2026 and will stop syncing data. New Fitbit developer accounts are no longer being issued.
Does Open Wearables still support Fitbit?
Yes, for workout and activity data, until the shutdown date. The integration is feature-frozen: Open Wearables is not adding new Fitbit data types, since the API itself is going away.
What Fitbit data does Open Wearables not support?
Sleep, intraday heart rate, and daily activity summary are available in the Fitbit Web API but were never implemented in Open Wearables, and will not be added given the shutdown.
What should I use instead of the Fitbit API?
The Google Health API. It is Google's cloud OAuth layer for Google Health data, and it aggregates data from Fitbit accounts, Health Connect, Google Fit, and other connected sources under one integration.
Which other providers can I connect alongside Fitbit?
Open Wearables currently integrates with Garmin, Polar, Whoop, Strava, Apple Health, Samsung Health, Google Health Connect, Suunto, and Oura. All providers share the same unified API schema.
Where is the Fitbit Web API documentation?
Fitbit's own developer documentation is at dev.fitbit.com. Open Wearables wraps the OAuth flow and activity endpoints documented there, so you do not need to implement the Fitbit Web API directly.
Is Open Wearables production-ready?
Yes. Open Wearables is actively maintained and used in production. Check the GitHub releases for the current status of each provider integration.
Open Wearables is built and maintained by Momentum, a digital health agency reshaping healthcare through technology. Since 2016, they have been turning medical discoveries into compliant, scalable digital solutions. Momentum offers commercial services on top of Open Wearables for teams that need custom integrations, enterprise deployment, or SLA-backed support.
themomentum.ai →Other integrations
Comparing options? See how Open Wearables compares to Terra, ROOK, Sahha and others →
One API. Every provider. Self-hosted.
Deploy Open Wearables on your infrastructure. MIT licensed. Self-hosted.