--- title: "Fitbit API Sunset: What Happens on the Sunset Date" canonical: "https://help.validic.com/space/VCS/5881036802/Fitbit%20API%20Sunset%3A%20What%20Happens%20on%20the%20Sunset%20Date" format: markdown --- ## A note on terminology There is no separate "Fitbit app" anymore. Google rebranded the Fitbit app to the Google Health app several months ago. Users now use the Google Health app on their device regardless of which Inform integration their data flows through. In this article: - Fitbit API refers to the legacy Google Fitbit Web API that Google is retiring, the data source behind Inform's Fitbit integration. - Fitbit integration refers to Inform's cloud source (`fitbit`) that pulls data from the Fitbit API. - Google Health API refers to Google's new platform and Inform's new cloud source (`google_health`) that replaces the Fitbit integration. ## Overview Google is retiring the Fitbit API on September 30, 2026. This is a firm date according to Google. After it passes, the Fitbit API stops working entirely, and any data flowing through Inform's Fitbit integration stops. This article explains what happens to the Fitbit integration and to your connected users at the point of sunset, and what that means for billing. ## What happens to the Fitbit integration at sunset When Inform sunsets a cloud source, the standard process is: - Users connected to that source are disconnected. - The source is removed from the Inform Marketplace in all orgs using it, so no new connections can be made to it. This is the pattern Inform follows for source sunsets generally, and it applies to the Fitbit integration as part of this transition. Inform plans to sunset the Fitbit integration on September 30, 2026, the same day Google retires the Fitbit API. As with the rest of this transition, the recommended path forward is to move your users from the Fitbit integration to the new Google Health API integration before that date, so their data continues flowing without interruption. See the [Fitbit to Google Health API Transition](https://help.validic.com/space/VCS/5436964886/Fitbit+to+Google+Health+API+Migration) section for the full migration timeline and steps. ## Billing Inform's cloud-source billing is per connected user, per cloud source, per month. A user is billable for a source for any month in which they were connected to that source during that month's billing usage window. The monthly billing usage window runs for the previous month. For example, the usage window that feeds the October billing run is August 26 through September 25. Because the Fitbit API does not shut down until September 30, a user who is connected to the Fitbit integration at any point within a given month's billing window is billable for that source for that cycle, even if their connection is later disconnected as part of the sunset process. In other words, being disconnected from the Fitbit integration at sunset does not retroactively remove billing for a cycle in which the connection was active. ## Alternative: mobile aggregators for clients not ready for Google Health API in production If your organization is not ready to move to the Google Health API cloud integration by September 30, 2026, there is another path for continuing to receive the data through Inform's mobile aggregators (Apple Health and Android Health Connect), if you already use one of those sources. An end user can connect the Google Health app to Apple Health or Android Health Connect on their device. When configured correctly, that mobile aggregator acts as a pass-through, and your organization continues receiving the same data that previously came through the Fitbit integration, now through the `apple_health` or `android_health_connect` source in your data stream. Users should update to the latest version of the Google Health app, since Google only introduced Apple Health connectivity as an option within the app in the last month or so. This path depends on the end user completing the mobile-side setup correctly, and it only applies to clients who already have Apple Health or Android Health Connect enabled as a source. It does not require your organization to have the Google Health API cloud integration live in production. If you don’t use the mobile agregators available through our SDK in production, then review the other options available in Inform: [https://help.validic.com/space/VCS/5847285761/The+Many+Activity+Trackers+Offered+by+ChartSpan](https://help.validic.com/space/VCS/5847285761/The+Many+Activity+Trackers+Offered+by+ChartSpan) ## What this means for you - Plan to migrate your users from the Fitbit integration to the Google Health API integration ahead of September 30, 2026, so their data keeps flowing without a gap. - Understand that users still connected to the Fitbit integration in the weeks before the sunset date will be reflected in that period's billing, independent of the sunset itself. - If you are not ready for the Google Health API integration in production, consider the Apple Health or Android Health Connect pass-through path described above. - If you go live with the Google Health cloud source at a later date, organization level backfill on cloud connections can be adjusted to ensure you get the data from the Fitbit API sunset until your user connects to Google Health in production. Organization-level backfill can be configured to 30, 180, or 360 days. If you are unsure what your production organization’s backfill is set to or want to change it ahead of your Google Health go live in production, reach out to the technical support team at [support@validic.com](mailto:support@validic.com) for assistance. - Subscribe to the [Inform status page](https://trust.validic.com/) for updates as September 30, 2026 approaches. ## Need Help? If you have questions about this transition or your account's Fitbit connections, reach out to your Inform contact or open a ticket with Inform Support by emailing [support@](mailto:support@validic.com)[validic.com](http://validic.com) or through the Inform Support Portal.