Identified - We've identified the root cause as a recent change in third-party API requirements that affects data collection. Our team is currently assessing the scope of impact and working with the vendor on resolution options.
We will provide additional details as our investigation progresses. Thank you for your patience.
Jul 09, 2026 - 09:16 EDT
We will provide additional details as our investigation progresses. Thank you for your patience.
Jul 09, 2026 - 09:16 EDT
Investigating - We are currently investigating possible delays in the delivery of data from Strava.
We will provide updates here as they are available.
Jul 08, 2026 - 09:37 EDT
We will provide updates here as they are available.
Jul 08, 2026 - 09:37 EDT
Update - We have updated our timeline for the iOS 26.6 fix based on the latest information from Apple's release schedule.
Current Status
iOS 26.6 includes the fix for the blood pressure permission issue. The update is currently in developer beta testing, with beta 4 released on July 6, 2026. Based on Apple's historical release patterns for point updates, we expect the public release to arrive in late July 2026, approximately July 27.
Revised Timeline
Our earlier projection of "early July" availability has been adjusted. iOS 26.6 with the fix will reach all users by late July.
What This Means for You
If you are experiencing the blood pressure permission issue on iOS 26.5:
- The workaround (Settings > Privacy & Security > Health > [app name] > toggle Blood Pressure on) remains available
- iOS 26.6, arriving in late July, includes the fix for this issue and will resolve the permission request problem
- Users who already granted blood pressure access on earlier iOS versions are not affected
- Both Inform SDK (2.x.x) and Legacy SDK (1.x.x) will benefit from this fix
We will provide another update once iOS 26.6 is released to the public.
Jul 08, 2026 - 15:27 EDT
Current Status
iOS 26.6 includes the fix for the blood pressure permission issue. The update is currently in developer beta testing, with beta 4 released on July 6, 2026. Based on Apple's historical release patterns for point updates, we expect the public release to arrive in late July 2026, approximately July 27.
Revised Timeline
Our earlier projection of "early July" availability has been adjusted. iOS 26.6 with the fix will reach all users by late July.
What This Means for You
If you are experiencing the blood pressure permission issue on iOS 26.5:
- The workaround (Settings > Privacy & Security > Health > [app name] > toggle Blood Pressure on) remains available
- iOS 26.6, arriving in late July, includes the fix for this issue and will resolve the permission request problem
- Users who already granted blood pressure access on earlier iOS versions are not affected
- Both Inform SDK (2.x.x) and Legacy SDK (1.x.x) will benefit from this fix
We will provide another update once iOS 26.6 is released to the public.
Jul 08, 2026 - 15:27 EDT
Update - iOS 26.6 Beta 2 (released June 15) continues to include the blood pressure permission fix noted in our previous update. Based on the beta release cadence, public availability is projected for early July, though Apple has not announced an official date. We will update this page when iOS 26.6 ships publicly and we have verified the fix.
Jun 30, 2026 - 13:14 EDT
Jun 30, 2026 - 13:14 EDT
Update - Apple has put out a developer beta for an upcoming iOS 26.6, and it fixes the Blood Pressure permission bug from iOS 26.5. There's no timeline yet for when iOS 26.6 will be released, and of course, we would need to verify the fix when it is available. Just wanted to note that this appears to be on Apple's radar, and they are planning to address it.
May 27, 2026 - 12:12 EDT
May 27, 2026 - 12:12 EDT
Update - Our ticket with Apple has been updated to the status of "potential fix identified for a future release." Since this is an iOS HealthKit regression, there isn't much Validic can do but track the status of the ticket we opened with Apple. We have not been given an ETA on when this will be addressed on the Apple side.
For any users on iOS 26.5 that encounter this, ask them to follow the workaround below:
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.
May 19, 2026 - 09:49 EDT
For any users on iOS 26.5 that encounter this, ask them to follow the workaround below:
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.
May 19, 2026 - 09:49 EDT
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
Degraded Performance
Tenovi
Operational
Whoop
Operational
Withings
Operational
Withings Pro
Operational
YOO
Operational
Zewa
Operational
TMC
Operational
Inform Infrastructure
Operational
Google Health
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
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 are completing our CASA certification before clients can transition to production with the Google Health integration in Inform. Our verification is underway, and the assessment begins when complete. If your CASA review starts before ours concludes, it will likely be flagged or blocked for unresolved third-party dependencies. Our certification completion will clear the way for your assessment.
For more information on the Google required CASA review and associated OAuth verification, please review this page: https://help.validic.com/space/VCS/5539037190/Requirements+and+Assessments+FAQs+for+Google+Health+API
While we finalize our certification, you can prepare now. CASA involves substantial documentation and prep work before formal auditing begins:
1. Gather existing certifications - SOC 2 or ISO 27002 documentation. (Note: ISO 27001 alone does not qualify). Assessors can map these to CASA requirements and skip redundant testing.
2. Start assessor conversations - Contact authorized App Defense Alliance assessors, complete scoping surveys, and compare quotes. Formal engagement begins after you receive Google's CASA notification email. https://appdefensealliance.dev/casa/casa-assessors
3. Audit and minimize OAuth scopes - Review which scopes your app requests and remove non-essential ones. Moving from Tier 3 to Tier 2 can reduce costs from 4500 USD to 500 USD and timelines from 4-6 weeks to 2-3 weeks.
4. Run pre-scan on staging - CASA follows OWASP ASVS standards. Test your staging environment now to identify issues like CORS problems or missing security headers: https://github.com/appdefensealliance/ASA-WG/blob/develop/CASA/CASA%20Specification.md
5. Prepare Google demo video - Record a video showing your OAuth grant process (in English), app details with OAuth client ID, and data usage demonstration. Google Drive or accessible file hosting works. This can be done in your lower environment
6. Check in-app disclosure - Google requires sensitive data use disclosure within the app during normal use, separate from privacy policy or website disclosures.
We will notify you immediately in this status page upon certification completion so you can begin your transition to production with our Google Health integration with minimal delay. Contact Validic support with questions.
Jul 08, 2026 - 15:18 EDT
For more information on the Google required CASA review and associated OAuth verification, please review this page: https://help.validic.com/space/VCS/5539037190/Requirements+and+Assessments+FAQs+for+Google+Health+API
While we finalize our certification, you can prepare now. CASA involves substantial documentation and prep work before formal auditing begins:
1. Gather existing certifications - SOC 2 or ISO 27002 documentation. (Note: ISO 27001 alone does not qualify). Assessors can map these to CASA requirements and skip redundant testing.
2. Start assessor conversations - Contact authorized App Defense Alliance assessors, complete scoping surveys, and compare quotes. Formal engagement begins after you receive Google's CASA notification email. https://appdefensealliance.dev/casa/casa-assessors
3. Audit and minimize OAuth scopes - Review which scopes your app requests and remove non-essential ones. Moving from Tier 3 to Tier 2 can reduce costs from 4500 USD to 500 USD and timelines from 4-6 weeks to 2-3 weeks.
4. Run pre-scan on staging - CASA follows OWASP ASVS standards. Test your staging environment now to identify issues like CORS problems or missing security headers: https://github.com/appdefensealliance/ASA-WG/blob/develop/CASA/CASA%20Specification.md
5. Prepare Google demo video - Record a video showing your OAuth grant process (in English), app details with OAuth client ID, and data usage demonstration. Google Drive or accessible file hosting works. This can be done in your lower environment
6. Check in-app disclosure - Google requires sensitive data use disclosure within the app during normal use, separate from privacy policy or website disclosures.
We will notify you immediately in this status page upon certification completion so you can begin your transition to production with our Google Health integration with minimal delay. Contact Validic support with questions.
Jul 08, 2026 - 15:18 EDT
Update -
Google has set a definitive date for the shutdown of the Fitbit Web API that Validic uses for the current Fitbit integration. Clients are advised to reach out to Validic support to start testing Google Health so that they will be ready when Google sunsets the Fitbit Web API and Validic is forced to shut down our current Fitbit integration:
September 30, 2026. This is the definitive calendar date when the legacy Fitbit Web API will be fully decommissioned and disabled.
Source: https://support.google.com/googlehealth/thread/438153444/clarification-on-fitbit-web-api-deprecation-timeline-and-oauth-consent-screen-changes?hl=en
Jun 17, 2026 - 09:09 EDT
September 30, 2026. This is the definitive calendar date when the legacy Fitbit Web API will be fully decommissioned and disabled.
Source: https://support.google.com/googlehealth/thread/438153444/clarification-on-fitbit-web-api-deprecation-timeline-and-oauth-consent-screen-changes?hl=en
Jun 17, 2026 - 09:09 EDT
Update -
Please follow the instructions in this document when creating Google Health credentials in Google Cloud Console. An Important Note was just added to avoid confusion and premature CASA triggering. I've copied the note below for awareness: https://help.validic.com/space/VCS/5581111299/Google+Health:+Getting+credentials+from+Google+Console
If your organization already has a Google Cloud Console project in Production mode used for other Google services (Google Fit, Google Maps, YouTube, or an Android application), do not add Google Health credentials to that project. Adding the Google Health API and its scopes to an existing Production-mode app can affect that app's OAuth verification status and could trigger a CASA security assessment for your existing production project.
The recommended path is to create a new, separate Google Cloud project dedicated to Google Health. This isolates the Google Health credential lifecycle from your existing production infrastructure and lets you test in Testing mode without any impact on your current users.
Jun 11, 2026 - 13:32 EDT
If your organization already has a Google Cloud Console project in Production mode used for other Google services (Google Fit, Google Maps, YouTube, or an Android application), do not add Google Health credentials to that project. Adding the Google Health API and its scopes to an existing Production-mode app can affect that app's OAuth verification status and could trigger a CASA security assessment for your existing production project.
The recommended path is to create a new, separate Google Cloud project dedicated to Google Health. This isolates the Google Health credential lifecycle from your existing production infrastructure and lets you test in Testing mode without any impact on your current users.
Jun 11, 2026 - 13:32 EDT
Update -
A couple of bugs and one piece of expected behavior we are tracking on the Google side that our clients who are testing should be aware of:
1. We have noticed that the Google Health API is returning timeouts intermittently. We have escalated this to Google and will update in this unique status page post: https://trust.validic.com/incidents/qnd7xjy4c63j
2. Google has acknowledged a bug that causes the step count delivered in the Google Health API to not match what is shown in the app. Google has escalated it to engineering. We will update as we learn more in this status page thread.
Expected behavior:
This was added to the bottom of this page in our documentation of things to be aware of when testing: https://help.validic.com/space/VCS/5581111299/Google+Health:+Getting+credentials+from+Google+Console#What-your-testers-should-be-aware-of-after-Google-Health-is-enabled-in-your-org
1. While your credentials are in the testing status in Google Cloud Console, Google is only allowing about 7 days of refresh token. We have seen a test user make it two weeks connected before being disconnected due to an invalid refresh token. If this happens to your user, you would need to reconnect your test user. This isn’t going to be a worry when credentials are in production status in Google Cloud Console, but while testing the integration in your sandbox, you may encounter this. You can see connection events org wide with this endpoint: https://developer.validic.com/reference/get-connection-events-by-orgid
Be aware that Google is still in active development on the Google Health API. We would generally wait until the vendor api is fully developed and stable to introduce a new source in our ecosystem, but due to the short runway with Google sunsetting the Fitbit APi in late August, we have tried to give our clients as much time as possible to test and become acquainted with the Google Health integration. We are in communication with Google and are adjusting to any breaking changes and adding any new metrics and endpoints as Google makes them available in their API. See this page for updates on what metrics are available today and ballpark estimates for when we will be able to introduce the metrics that Google is working to make available: https://help.validic.com/space/VCS/5436080132/Fitbit+to+Google+Health+API+Metric+Mapping+Guide#How-to-Read-This-Guide
If anyone has any questions about this new source, send an email to support@validic.com to open a ticket with our technical support team. We are here to help you through this transition with any questions that may come up.
Jun 11, 2026 - 09:27 EDT
1. We have noticed that the Google Health API is returning timeouts intermittently. We have escalated this to Google and will update in this unique status page post: https://trust.validic.com/incidents/qnd7xjy4c63j
2. Google has acknowledged a bug that causes the step count delivered in the Google Health API to not match what is shown in the app. Google has escalated it to engineering. We will update as we learn more in this status page thread.
Expected behavior:
This was added to the bottom of this page in our documentation of things to be aware of when testing: https://help.validic.com/space/VCS/5581111299/Google+Health:+Getting+credentials+from+Google+Console#What-your-testers-should-be-aware-of-after-Google-Health-is-enabled-in-your-org
1. While your credentials are in the testing status in Google Cloud Console, Google is only allowing about 7 days of refresh token. We have seen a test user make it two weeks connected before being disconnected due to an invalid refresh token. If this happens to your user, you would need to reconnect your test user. This isn’t going to be a worry when credentials are in production status in Google Cloud Console, but while testing the integration in your sandbox, you may encounter this. You can see connection events org wide with this endpoint: https://developer.validic.com/reference/get-connection-events-by-orgid
Be aware that Google is still in active development on the Google Health API. We would generally wait until the vendor api is fully developed and stable to introduce a new source in our ecosystem, but due to the short runway with Google sunsetting the Fitbit APi in late August, we have tried to give our clients as much time as possible to test and become acquainted with the Google Health integration. We are in communication with Google and are adjusting to any breaking changes and adding any new metrics and endpoints as Google makes them available in their API. See this page for updates on what metrics are available today and ballpark estimates for when we will be able to introduce the metrics that Google is working to make available: https://help.validic.com/space/VCS/5436080132/Fitbit+to+Google+Health+API+Metric+Mapping+Guide#How-to-Read-This-Guide
If anyone has any questions about this new source, send an email to support@validic.com to open a ticket with our technical support team. We are here to help you through this transition with any questions that may come up.
Jun 11, 2026 - 09:27 EDT
Update -
Instructions for how to get your credentials for sandbox testing with Google Health are available now: https://help.validic.com/space/VCS/5581111299/Google+Health:+Getting+credentials+from+Google+Console
Once you create those, open a ticket with Validic technical support by sending an email to support@validic.com, cc any colleagues that need to be aware of the communication, and deliver the file downloaded in the process with your credentials, a screenshot of the scopes selected for the credentials, and your sandbox organization ID. Those three pieces of information are required to set up Google Health in your sandbox so your organization can test the new integration.
May 26, 2026 - 09:29 EDT
Once you create those, open a ticket with Validic technical support by sending an email to support@validic.com, cc any colleagues that need to be aware of the communication, and deliver the file downloaded in the process with your credentials, a screenshot of the scopes selected for the credentials, and your sandbox organization ID. Those three pieces of information are required to set up Google Health in your sandbox so your organization can test the new integration.
May 26, 2026 - 09:29 EDT
Update -
We're close to letting clients test Google Health integration in their sandboxes. Updates will be coming soon on that.
We're hosting a free webinar on May 27 at 2 PM ET specifically to walk your team through what this migration from the current Fitbit integration to the Google Health integration entails. It's more involved than a simple config change; it touches your data pipeline, your marketplace reconnection flow, and potentially parts of your data model. The sooner your engineers have a clear picture of the scope, the better.
Register here: https://validic.zoom.us/webinar/register/3417792240109/WN_b9x0TULDS3KaO7e9jBXqhw
May 20, 2026 - 16:23 EDT
We're hosting a free webinar on May 27 at 2 PM ET specifically to walk your team through what this migration from the current Fitbit integration to the Google Health integration entails. It's more involved than a simple config change; it touches your data pipeline, your marketplace reconnection flow, and potentially parts of your data model. The sooner your engineers have a clear picture of the scope, the better.
Register here: https://validic.zoom.us/webinar/register/3417792240109/WN_b9x0TULDS3KaO7e9jBXqhw
May 20, 2026 - 16:23 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