Fitbit API for personal use after the Google migration

The legacy Fitbit Web API has been shut down, so personal scripts that called it need Google's replacement or another route. For your own Android phone, one option is reading Health Connect through HC Sync, free for 5 synced users in public beta.

Last updated: 2026-11-07. Dates quoted from Google and Fitbit pages fetched on 2026-11-07.

Key facts (as of 2026-11)

What happened to the Fitbit API?

Fitbit's developer documentation says "Support for the legacy Fitbit Web API ends on September 30, 2026" and that on 30 October 2026 the API "will be turned off and will no longer function or sync data to or from Fitbit users." It tells developers to migrate to the Google Health API. Google's own Health API page gives 2 November 2026 as the shutdown date for the legacy API and Fitbit OAuth endpoints. Either way, old personal access tokens and client IDs should be treated as dead.

Can you still use a Fitbit API key for personal use?

Not the old one. Fitbit's page only states that anyone may use the Web APIs to build integrations, subject to the platform terms and developer policy, and that was for the legacy API. Whether Google offers an easier route for a single-person project is not stated on the pages we read, and we will not guess. Check the Google Health API documentation; its getting-started material points to a codelab and Google's OAuth 2.0 Playground for a first call. Also check whether your scopes require verification before you add other users.

What is the Google Health API route?

It is a cloud API: your server holds a Google OAuth grant for each user and calls Google, much as it called Fitbit. Existing Fitbit users generally have to reconnect through Google OAuth. It suits server-to-server access to Fitbit and Pixel Watch data. See Google Health API alternative for a comparison with the Android route.

What is the Android Health Connect route?

If you and your users are on Android and your Fitbit data reaches Health Connect, an app on the phone can read it on-device and upload it. Check in the Health Connect app which apps are writing the data types you want; HC Sync only transports what Health Connect contains. HC Sync's SDK reads permitted records, uploads them and gives your backend REST reads, signed webhooks and read-only MCP.

curl "https://hcsync.dev/v1/summary?user_id=me&days=7&tz=Europe/London" \
  -H "authorization: Bearer $HCSYNC_READ_KEY"

Which option fits a personal project?

HC Sync is in public beta. The free plan is for testing and pilots. Paid plans are open: Starter ($29/month) and Indie ($149/month) check out through Paddle. See Fitbit Web API migration for an endpoint map from Fitbit calls to HC Sync reads.

Official sources

Common questions

Does the Fitbit Web API still work?

No. Fitbit’s developer page says it was turned off on 30 October 2026, and Google’s Health API page gives 2 November 2026. Migrate to the Google Health API or another route.

Can I get a Fitbit API key for personal use?

The legacy API is off. The Google pages we read do not describe a personal-use tier, so check the Google Health API documentation for current rules.

Can HC Sync read my Fitbit data?

Only if that data is in Android Health Connect on your phone. HC Sync reads Health Connect and does not connect to Fitbit’s cloud.

Does this work on iPhone?

No. Health Connect is Android only.

Fitbit Web API migration · Google Health API alternative · Google Fit API replacement · Health Connect REST API · HC Sync documentation

Create a free project