We have been making progress on having the Google Health integration ready for our clients to test in their sandbox. We're not quite there yet, but updates will be coming as we reach that milestone.
What's coming next? -We will be providing documentation to guide our clients on the steps they need to take to go through the steps on Google's side to get developer credentials to share with our support team, so we can enable Google Health in your sandbox with your unique developer credentials. This will be made available when we have the integration ready for sandbox testing.
-Before taking the steps to create your developer credentials, you need to look at what your organization uses from Fitbit currently and use that to guide what scopes you will add to your developer credentials for Google Health. You should only select the scopes you actually ingest and use in your application. You should only select scopes that are currently supported by our coming Google Health integration.
We're excited about the Google Health integration, but we know that a lot of our clients still have questions about what the transition from the existing Fitbit integration to the Google Health integration will be like. You can ask all questions by reaching out to our support team at support@validic.com. We're always here to help!
The end user's app is Fitbit today and will continue to be that until the change on May 19th, 2026, when it is rebranded as Google Health
Posted May 11, 2026 - 15:59 EDT
Update
As an update, the integration for Google Health API will be available for sandbox testing in Inform in late May. Additionally, we have created this document to help with some clarification of the review process that Google is planning for the use of the Google Health API. If you have any questions about any of this, feel free to open a support ticket by emailing support@validic.com so we can assist further https://help.validic.com/space/VCS/5535203416/Fitbit+to+Google+Health+API:+Developer+Migration+Timeline
Posted May 06, 2026 - 15:48 EDT
Update
Google is replacing the Fitbit Web API with the Google Health API. All Validic clients currently using the Fitbit cloud integration will need to transition to the new Google Health API integration before September 2026, when the legacy Fitbit Web API will be decommissioned. Both integrations will run side by side from May through September; there is no planned downtime.
What's new: - Validic's Google Health API integration will be available for testing in the Inform Marketplace in early May 2026. Google recommends production launches begin in late May. - Clients will need to register directly with Google for developer credentials. Validic will provide the necessary callback URL and setup information. Please wait to create your developer credentials until we have our integration finalized so we can share best practices to ensure they work seamlessly with our platform. - The Google Health API accesses restricted scopes, the highest category under Google's OAuth verification framework. Full app verification, a security assessment, and annual re-verification are required before going to production. Details on Google's verification process: https://support.google.com/cloud/answer/13463073 - While you should wait for Validic's outreach before requesting developer credentials, you can begin verification groundwork now: prepare your homepage, privacy policy, domain verification, demo video, and scope justifications. Getting ahead on these steps will give your team more runway once development begins.
Key dates: - Now — Begin OAuth app verification groundwork (no credentials needed for this step) - Early May 2026 — Google Health API source available in Validic Marketplace (testing) - May 19, 2026 — Fitbit users who haven't migrated their login to a Google Account lose access to Fitbit (separate status page: https://trust.validic.com/incidents/hp77lmtp130s) - Late May 2026 — Google's recommended production launch window - September 2026 — Legacy Fitbit Web API decommissioned
Important: This transition is separate from the Fitbit-to-Google Account login migration (May 19 deadline), which is tracked on a separate status page: https://trust.validic.com/incidents/hp77lmtp130s. End users need to complete both actions: the account login migration AND reconnecting through the new Google Health API integration.
We will share detailed migration documentation, including a data mapping guide and a developer migration guide, as they are finalized. Subscribe to this page for updates.
Posted Apr 09, 2026 - 15:01 EDT
Update
We have added some integration details and support guides for this transition.
The timeline remains that this source won't be available until May 2026, but we are getting this information ahead of time so that our clients can plan for this transition. After reading all our documentation, if you still have questions, reach out to Validic technical support so we can assist. These documents will be updated as new information becomes available about this coming source in the Inform ecosystem.
This will require action from your users and your dev team. We've been preparing for this and are here to help you through it.
- - -
Here's the timeline: - May 2026: The new Google Health API integration becomes available in your Inform marketplace. You'll need to request it be added on or after this date to get started. - May 19, 2026: Fitbit users must transition to a Google Account before this date, or they'll lose access to the Fitbit app and data syncing. For more information, see [maintenance PAGE](https://trust.validic.com/incidents/hp77lmtp130s). - September 2026: The legacy Fitbit Web API shuts down for good. All connections must be migrated by then, or data will stop syncing.
- - -
What this means for your users: - Every Fitbit user will need to reconnect through the new Google Health API integration. Google requires each user to sign in with their Google Account and grant permissions.
- - -
What this means for your dev team: - Google Health is a new integration, available in May 2026 in your Inform marketplace. – If you are currently using the Validic v1 (legacy) API, please reach out to our support team for assistance: https://help.validic.com/portal/2 - Plan to update any logic referencing the "fitbit" source type to also handle "google_health". Your data still comes through as the same Validic standard objects. Some metric names have changed, and we'll have a mapping guide available soon. There is no downtime currently planned as part of this transition. Both integrations will run side by side from May through September 2026. And we have dedicated contacts at Google supporting this transition and will make sure any questions get to the right people.
- - -
We know transitions like this can feel like a lot, but this is exactly the kind of thing Validic is here for. We’re preparing additional information for you, which we plan to post next week. We will also continue to provide updated information as it is available through this maintenance page.