Identified - Apple released iOS 26.5 today with a HealthKit regression that prevents blood pressure permission requests from completing correctly. This affects only Inform clients receiving blood pressure data through the measurement endpoint via Apple Health.
Scope is narrow: only users who grant blood pressure permission for the first time on iOS 26.5 are affected. Users who authorized blood pressure access on iOS 26.4.2 or earlier are unaffected and will continue to see data. Bluetooth-collected blood pressure readings are not affected.
Workaround: Affected users can manually enable access via Settings > Privacy & Security > Health > [your app name], then toggle Blood Pressure on. Data flows normally once this is done.
Apple Developer Relations has confirmed this is a regression. We have filed a support incident and will update this page when a fix is available. The fix would need to be on the Apple side to be clear.
May 11, 2026 - 15:51 EDT
Scope is narrow: only users who grant blood pressure permission for the first time on iOS 26.5 are affected. Users who authorized blood pressure access on iOS 26.4.2 or earlier are unaffected and will continue to see data. Bluetooth-collected blood pressure readings are not affected.
Workaround: Affected users can manually enable access via Settings > Privacy & Security > Health > [your app name], then toggle Blood Pressure on. Data flows normally once this is done.
Apple Developer Relations has confirmed this is a regression. We have filed a support incident and will update this page when a fix is available. The fix would need to be on the Apple side to be clear.
May 11, 2026 - 15:51 EDT
About This Site
We continuously monitor the status of the Validic Inform APIs and all its related services. If there are any interruptions in service, a note will be posted here. If you are experiencing problems connecting to Validic and do not see a notice posted here, please visit support.validic.com to review our knowledge base articles for quick troubleshooting support. If your issue is not addressed there, please email support@validic.com with your company name, organization ID and user ID for the user experiencing issues, if necessary, and any other supporting information that may help expedite the resolution of your support request.
For Validic V1 API status, visit http://status.validic.com
Streaming API
Operational
REST API
Operational
Inform SDK (2.x.x)
Operational
Legacy SDK (1.x.x)
Operational
Inform Marketplace
Operational
Push Service
Operational
Support Portal
Operational
API Documentation
Operational
QuickSight Reporting
Operational
Abbott
Operational
AsthmaMD
Operational
BodiMetrics
Operational
BodyTrace
Operational
Dario
Operational
Dexcom
Operational
Emfit
Operational
Fitbit
Operational
Foracare
Operational
Garmin Connect
Operational
Higi
Operational
iHealth
Operational
Keto-Mojo
Operational
LifeScan/OneTouch
Operational
MapMyFitness
Operational
MyFitnessPal
Operational
Omron
Operational
Omron Japan
Operational
Oura
Operational
Philips
Operational
Polar
Operational
Runkeeper
Operational
Smart Meter
Operational
Stel
Operational
Strava
Operational
Tenovi
Operational
Whoop
Operational
Withings
Operational
Withings Pro
Operational
YOO
Operational
Zewa
Operational
TMC
Operational
Inform Infrastructure
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Important: Fitbit Account Changes - Action Needed by May 2026 May 19, 2026 00:00-00:01 EDT
Update -
This shift of auth by Google is part of a bigger migration. See the full picture here: https://trust.validic.com/incidents/8lzmtg20hp90
Apr 02, 2026 - 15:55 EDT
Apr 02, 2026 - 15:55 EDT
Update -
Google Fitbit has extended the deadline to move all Fitbit Accounts to Google Accounts to May 19, 2026. They have posted the full details of this process here: https://support.google.com/fitbit/answer/14237024
All of the previous information that Validic has shared about this is still accurate. Only the date has changed.
Jan 30, 2026 - 15:47 EST
All of the previous information that Validic has shared about this is still accurate. Only the date has changed.
Jan 30, 2026 - 15:47 EST
Update -
If you and your team are aware of this and have already taken action regarding it, then please ignore this reminder. Validic is just trying to make sure our clients are prepared for this change on the Fitbit side so that your end users aren't caught off guard.
Google is finalizing the transition away from legacy Fitbit accounts. Beginning February 2, 2026, users must move their Fitbit account to a Google Account if they want to continue syncing data. If the migration hasn’t been completed by that date, the user’s Fitbit login will stop working, historical health data will no longer be accessible, and they will need to reauthorize in Inform once they complete the move.
What your end users must do:
-Open the Fitbit app on their smartphone (iOS or Android).
-Tap their profile or settings icon.
-Look for Move Account and follow the on-screen prompts to transfer their Fitbit account to a Google Account.
-If they don’t see the prompt, it may appear after updating the Fitbit app to the latest version.
-If they don’t already have a Google Account, they’ll be prompted to create one during the process.
Important notes to share with your users:
-The process generally takes just a few minutes and preserves their Fitbit history and device connections.
-A personal Google Account is required (Google Workspace accounts typically won’t work).
-Failure to migrate by Feb. 2, 2026, will result in Fitbit data no longer syncing, and they’ll need to re-authenticate after moving their accounts.
Helpful Support Articles:
Fitbit’s step-by-step guide from Google Help:
https://support.google.com/fitbit/answer/14237024?hl=en
Validic support article (guidance for migrating Fitbit users):
https://help.validic.com/space/VCS/3755213034/Moving+a+Fitbit+user+to+a+Google+Account
Please consider circulating this notice to your users as soon as possible. If you need a templated communication for your user base or have questions on how this impacts your Inform integration, let us know by emailing support@validic.com
Jan 14, 2026 - 09:08 EST
Google is finalizing the transition away from legacy Fitbit accounts. Beginning February 2, 2026, users must move their Fitbit account to a Google Account if they want to continue syncing data. If the migration hasn’t been completed by that date, the user’s Fitbit login will stop working, historical health data will no longer be accessible, and they will need to reauthorize in Inform once they complete the move.
What your end users must do:
-Open the Fitbit app on their smartphone (iOS or Android).
-Tap their profile or settings icon.
-Look for Move Account and follow the on-screen prompts to transfer their Fitbit account to a Google Account.
-If they don’t see the prompt, it may appear after updating the Fitbit app to the latest version.
-If they don’t already have a Google Account, they’ll be prompted to create one during the process.
Important notes to share with your users:
-The process generally takes just a few minutes and preserves their Fitbit history and device connections.
-A personal Google Account is required (Google Workspace accounts typically won’t work).
-Failure to migrate by Feb. 2, 2026, will result in Fitbit data no longer syncing, and they’ll need to re-authenticate after moving their accounts.
Helpful Support Articles:
Fitbit’s step-by-step guide from Google Help:
https://support.google.com/fitbit/answer/14237024?hl=en
Validic support article (guidance for migrating Fitbit users):
https://help.validic.com/space/VCS/3755213034/Moving+a+Fitbit+user+to+a+Google+Account
Please consider circulating this notice to your users as soon as possible. If you need a templated communication for your user base or have questions on how this impacts your Inform integration, let us know by emailing support@validic.com
Jan 14, 2026 - 09:08 EST
Update -
Google is finalizing the transition away from legacy Fitbit accounts. Beginning February 2, 2026, users must move their Fitbit account to a Google Account if they want to continue syncing data. If the migration hasn’t been completed by that date, the user’s Fitbit login will stop working, historical health data will no longer be accessible, and they will need to reauthorize in Inform once they complete the move.
What your end users must do:
-Open the Fitbit app on their smartphone (iOS or Android).
-Tap their profile or settings icon.
-Look for Move Account and follow the on-screen prompts to transfer their Fitbit account to a Google Account.
-If they don’t see the prompt, it may appear after updating the Fitbit app to the latest version.
-If they don’t already have a Google Account, they’ll be prompted to create one during the process.
Important notes to share with your users:
-The process generally takes just a few minutes and preserves their Fitbit history and device connections.
-A personal Google Account is required (Google Workspace accounts typically won’t work).
-Failure to migrate by Feb. 2, 2026, will result in Fitbit data no longer syncing, and they’ll need to re-authenticate after moving their accounts.
Helpful Support Articles:
Fitbit’s step-by-step guide from Google Help:
https://support.google.com/fitbit/answer/14237024?hl=en
Validic support article (guidance for migrating Fitbit users):
https://help.validic.com/space/VCS/3755213034/Moving+a+Fitbit+user+to+a+Google+Account
Please consider circulating this notice to your users as soon as possible. If you need a templated communication for your user base or have questions on how this impacts your Inform integration, let us know by emailing support@validic.com
Additionally, note the following:
For Fitbit Developer Accounts:
* Do you have your own Fitbit developer account on dev.fitbit.com?
* You *must* migrate this account to a Google Account.
* If you don't switch, you will:
- Lose API access
- Can't log into your developer account
- Lose all app and integration data
Is Validic managing your developer credentials?
- Validic does manage a large number of developer credentials for our clients. That being the case...
- You likely don't need to do anything.
- We'll handle the transition.
Jan 05, 2026 - 11:40 EST
What your end users must do:
-Open the Fitbit app on their smartphone (iOS or Android).
-Tap their profile or settings icon.
-Look for Move Account and follow the on-screen prompts to transfer their Fitbit account to a Google Account.
-If they don’t see the prompt, it may appear after updating the Fitbit app to the latest version.
-If they don’t already have a Google Account, they’ll be prompted to create one during the process.
Important notes to share with your users:
-The process generally takes just a few minutes and preserves their Fitbit history and device connections.
-A personal Google Account is required (Google Workspace accounts typically won’t work).
-Failure to migrate by Feb. 2, 2026, will result in Fitbit data no longer syncing, and they’ll need to re-authenticate after moving their accounts.
Helpful Support Articles:
Fitbit’s step-by-step guide from Google Help:
https://support.google.com/fitbit/answer/14237024?hl=en
Validic support article (guidance for migrating Fitbit users):
https://help.validic.com/space/VCS/3755213034/Moving+a+Fitbit+user+to+a+Google+Account
Please consider circulating this notice to your users as soon as possible. If you need a templated communication for your user base or have questions on how this impacts your Inform integration, let us know by emailing support@validic.com
Additionally, note the following:
For Fitbit Developer Accounts:
* Do you have your own Fitbit developer account on dev.fitbit.com?
* You *must* migrate this account to a Google Account.
* If you don't switch, you will:
- Lose API access
- Can't log into your developer account
- Lose all app and integration data
Is Validic managing your developer credentials?
- Validic does manage a large number of developer credentials for our clients. That being the case...
- You likely don't need to do anything.
- We'll handle the transition.
Jan 05, 2026 - 11:40 EST
Scheduled -
Google is moving all Fitbit accounts to Google Accounts. This change affects every Fitbit user and developer. You'll need to take steps to keep using Fitbit services and APIs.
Key Dates You Should Know:
* Now: Fitbit users can start moving to Google Accounts.
* February 2, 2026: All Fitbit users *must* switch to a Google Account.
- After this date, your old Fitbit login will stop working.
- You'll lose access to your Fitbit account and data if you don't switch.
What You Need to Do:
1. For Fitbit Users:
* All Validic users with Fitbit accounts must move to a Google Account.
* The switch is optional now, but required by February 2026.
* Tell your users to prepare for this change.
2. For Fitbit Developer Accounts:
* Do you have your own Fitbit developer account on dev.fitbit.com?
* You *must* migrate this account to a Google Account.
* If you don't switch, you will:
- Lose API access
- Can't log into your developer account
- Lose all app and integration data
Is Validic managing your developer credentials?
- Validic does manage a large number of developer credentials for our clients. That being the case...
- You likely don't need to do anything.
- We'll handle the transition.
- Still unsure? Contact support: https://help.validic.com/portal/2
Our team is working hard to make this transition smooth. We'll keep you updated as Google provides more details.
Need help? Reach out to our support team: https://help.validic.com/portal/2
We also have an FAQ you can review: https://help.validic.com/space/VCS/3755213034/Moving+a+Fitbit+user+to+a+Google+Account
See Google’s instructions: https://support.google.com/fitbit/answer/14237024
Jul 21, 2025 - 16:03 EDT
Key Dates You Should Know:
* Now: Fitbit users can start moving to Google Accounts.
* February 2, 2026: All Fitbit users *must* switch to a Google Account.
- After this date, your old Fitbit login will stop working.
- You'll lose access to your Fitbit account and data if you don't switch.
What You Need to Do:
1. For Fitbit Users:
* All Validic users with Fitbit accounts must move to a Google Account.
* The switch is optional now, but required by February 2026.
* Tell your users to prepare for this change.
2. For Fitbit Developer Accounts:
* Do you have your own Fitbit developer account on dev.fitbit.com?
* You *must* migrate this account to a Google Account.
* If you don't switch, you will:
- Lose API access
- Can't log into your developer account
- Lose all app and integration data
Is Validic managing your developer credentials?
- Validic does manage a large number of developer credentials for our clients. That being the case...
- You likely don't need to do anything.
- We'll handle the transition.
- Still unsure? Contact support: https://help.validic.com/portal/2
Our team is working hard to make this transition smooth. We'll keep you updated as Google provides more details.
Need help? Reach out to our support team: https://help.validic.com/portal/2
We also have an FAQ you can review: https://help.validic.com/space/VCS/3755213034/Moving+a+Fitbit+user+to+a+Google+Account
See Google’s instructions: https://support.google.com/fitbit/answer/14237024
Jul 21, 2025 - 16:03 EDT
Philips BioTel Care Shutting Down Jul 24, 2026 00:00-00:01 EDT
Philips will be shutting down its BioTel Care remote patient monitoring platform and TelServe services on July 24, 2026.
As a result, cellular blood glucose devices operating through the Philips Inform cloud integration will stop transmitting data, and third-party applications will no longer receive any data through the integration. Users will also be unable to establish new connections through Philips after that date.
If you have any questions, please reach out to the Validic support team or your Philips business contact for assistance.
Posted on Mar 20, 2026 - 10:20 EDT
As a result, cellular blood glucose devices operating through the Philips Inform cloud integration will stop transmitting data, and third-party applications will no longer receive any data through the integration. Users will also be unable to establish new connections through Philips after that date.
If you have any questions, please reach out to the Validic support team or your Philips business contact for assistance.
Posted on Mar 20, 2026 - 10:20 EDT
Fitbit Is Becoming Google Health API - Key Dates Sep 30, 2026 12:13-13:13 EDT
Update -
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.
For clarity on what scopes on the Google side map to what endpoints on the Validic side, see this documentation: https://help.validic.com/space/VCS/5535203416/Fitbit+to+Google+Health+API:+Developer+Migration+Timeline#Before-May---Scope-Review-and-Assessor-Research
For clarity on what metrics will be available in what endpoint for Google Health, scroll down to the Google Health entry on this page: https://help.validic.com/space/VCS/1681129566/Standard+Metrics+Used+per+App
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!
May 14, 2026 - 13:51 EDT
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.
For clarity on what scopes on the Google side map to what endpoints on the Validic side, see this documentation: https://help.validic.com/space/VCS/5535203416/Fitbit+to+Google+Health+API:+Developer+Migration+Timeline#Before-May---Scope-Review-and-Assessor-Research
For clarity on what metrics will be available in what endpoint for Google Health, scroll down to the Google Health entry on this page: https://help.validic.com/space/VCS/1681129566/Standard+Metrics+Used+per+App
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!
May 14, 2026 - 13:51 EDT
Update -
Google has announced that on May 19, 2026, the Fitbit app will be rebranded as Google Health. See their announcement here: https://support.google.com/fitbit/answer/17068213?hl=en&ref_topic=14236398&sjid=8074733428172977564-NA
Additionally, they shared this page with some more information on the Google Health app requirements: https://support.google.com/product-documentation/answer/14226283
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
May 11, 2026 - 15:59 EDT
Additionally, they shared this page with some more information on the Google Health app requirements: https://support.google.com/product-documentation/answer/14226283
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
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
May 06, 2026 - 15:48 EDT
https://help.validic.com/space/VCS/5535203416/Fitbit+to+Google+Health+API:+Developer+Migration+Timeline
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.
Apr 09, 2026 - 15:01 EDT
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.
Apr 09, 2026 - 15:01 EDT
Update -
We have added some integration details and support guides for this transition.
Google Health API Integration page: https://help.validic.com/space/VCS/5435195394/Google+Health+API+Integration+for+Developers
Google Health API migration guides:
https://help.validic.com/space/VCS/5436964886/Fitbit+to+Google+Health+Migration
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.
Apr 02, 2026 - 15:42 EDT
Google Health API Integration page: https://help.validic.com/space/VCS/5435195394/Google+Health+API+Integration+for+Developers
Google Health API migration guides:
https://help.validic.com/space/VCS/5436964886/Fitbit+to+Google+Health+Migration
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.
Apr 02, 2026 - 15:42 EDT
Scheduled -
Google has announced the next generation of their health data platform: the Google Health API, replacing the legacy Fitbit Web API. You can read their full announcement here: https://community.fitbit.com/t5/Web-API-Development/Introducing-the-next-phase-of-the-Fitbit-Web-API/m-p/5821061
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.
Mar 27, 2026 - 12:17 EDT
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.
Mar 27, 2026 - 12:17 EDT