Fitbit: do not register a new app

#What to do

• New integrations: skip Fitbit and register a Google Health app instead.
• Existing Fitbit apps: they work until 2 Nov 2026. Use the remaining days only for a one-off backfill, then:
  • Fitbit tokens cannot be migrated: every member re-consents through Google Health [OFF].
  • Members must link their Fitbit account to a Google Account, otherwise Google Health returns 400 FAILED_PRECONDITION / ACCOUNT_NOT_LINKED [OFF].
  • Do not keep both links: revoke the Fitbit tokens once the Google Health connection works [OFF].

#If you must register one before the turn-off

Only for a backfill of your own data before 2 Nov 2026 [MEM]:

1. https://dev.fitbit.com/apps/new, signed in with the Fitbit (Google) account.
2. OAuth 2.0 application type: Server. Redirect URL: https://api.getlatido.com/connect/callback/fitbit.
3. Paste Client ID and Client Secret in Latido, Providers → Fitbit → Custom app.

#Sources

• https://developers.google.com/health/about (updated 2026-10-23)
• https://developers.google.com/health/migration
• https://dev.fitbit.com/build/reference/web-api/ [MEM]