Important updates to the Fitbit Web APIs
chevron down
back search icon cancel search

Important updates to the Fitbit Web APIs

Dear Fitbit Developer Community,

We’re making some important upgrades to the Fitbit APIs so that they remain stable and scalable for everyone. To ensure your applications continue to work seamlessly, please note and take action on the following changes, some of which have already started to roll out and others will be rolled out over the rest of 2025:

  • Transition to 64-bit Identifiers: We are upgrading the database that stores our log ID identifiers. This allows all Fitbit data types (e.g., Sleep, Activity) to support 64-bit log ID identifiers. With this change, your systems must be able to handle 64-bit integer IDs to avoid data truncation and errors. Update now if they are not.
  • Updated Log ID values: As part of the database migration, you may observe Log ID values have changed. If you store Fitbit log ID identifiers and you want to retain continuity with a users historical data, ensure you match the data associated with the new log ID against the data with the old log ID when you reconcile your stored data.
  • Stricter Syntax Enforcement: We are improving our system to properly validate endpoint syntax. Endpoints that previously accepted incorrect syntax or wrong version numbers may now return an error message. Please review the official documentation to confirm your application is using the correct syntax and endpoint versions.
  • Deprecation of Sleep v1: The Sleep v1 endpoints, deprecated since 2016, will no longer be accessible. They have not been actively maintained, do not support sleep stages, and may return incorrect data. If your application still uses Sleep v1, please upgrade to Sleep v1.2 as soon as possible.

Timeline: These changes have started rolling out and will continue to do so throughout 2025. As a short-term measure to help you through the transition, we have deployed a temporary patch to prevent Log ID errors on delete or update endpoints. The patch will be removed at the end of the 2025.

Thank you for being such an important part of the Fitbit ecosystem. Your partnership helps us build a more robust and reliable platform for everyone.

Best,

The Google Fitbit Team