Newest Legacy and Inform iOS Native SDK versions for Apple Health summary query optimization
Subscribe
Identified - This is less of reporting an issue and more for noting a fix for something Validic noticed about Apple iOS 26 and summary records. Apple has always surfaced old summary records as new records in their HealthKit api as part of their housekeeping. In iOS 26, it appears this can happen much more frequently. Apple has acknowledged this is a bug in iOS 26. In versions older than Legacy iOS Native 1.18.0 and Inform iOS Native 2.1.0, in certain situations, the SDK would process that old record and then query every summary record since then. This creates a large volume of redundant summary records and slows the speed at which new data is ingested for users. More information about this is on this KBA: https://help.validic.com/space/VCS/4957044737/Apple+Health+Summary+Record+Volume+Improvements
Clients using the Apple Health/HealthKit module in the Validic SDK are encouraged to update to Legacy iOS Native 1.18.0 or Inform iOS Native 2.1.0 to mitigate this and have the best performance they can with our integration with the HealthKit API
If you or your team has any questions about the information above or in the linked KBA, open a ticket with Validic technical support by emailing support@validic.com
Oct 17, 2025 - 13:04 EDT
Clients using the Apple Health/HealthKit module in the Validic SDK are encouraged to update to Legacy iOS Native 1.18.0 or Inform iOS Native 2.1.0 to mitigate this and have the best performance they can with our integration with the HealthKit API
If you or your team has any questions about the information above or in the linked KBA, open a ticket with Validic technical support by emailing support@validic.com
Oct 17, 2025 - 13:04 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
Lose It
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
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Garmin Connect updates to guidelines for use of its API Nov 1, 2025 09:57-10:57 EDT
Garmin has updated its guidelines for the use of its Garmin Connect API. There is a new clause added that indicates that clients must display one of the following anywhere that they display Garmin-generated data.
*Garmin
*Garmin and/or Garmin Connect logos
*Garmin, Garmin Connect, and/or Garmin mountain bike dynamics (including Grit™ and Flow™) word marks
Validic uses the Garmin logo in our marketplace, so our clients can use that logo. If you need any additional logos mentioned above, then open a support ticket with us so that we can give you the logos you need. Garmin has them available behind the developer account login, which we can access. If any clients need the Garmin Connect Developer Program Agreement that states these changes, we are happy to deliver that in a support ticket as well.
Garmin has given a deadline of November 1, 2025 for these changes to be addressed. Reach out to support@validic.com if you have any questions about this information.
Posted on Jul 02, 2025 - 10:02 EDT
*Garmin
*Garmin and/or Garmin Connect logos
*Garmin, Garmin Connect, and/or Garmin mountain bike dynamics (including Grit™ and Flow™) word marks
Validic uses the Garmin logo in our marketplace, so our clients can use that logo. If you need any additional logos mentioned above, then open a support ticket with us so that we can give you the logos you need. Garmin has them available behind the developer account login, which we can access. If any clients need the Garmin Connect Developer Program Agreement that states these changes, we are happy to deliver that in a support ticket as well.
Garmin has given a deadline of November 1, 2025 for these changes to be addressed. Reach out to support@validic.com if you have any questions about this information.
Posted on Jul 02, 2025 - 10:02 EDT
Important: Fitbit Account Changes - Action Needed by February 2026 Feb 2, 2026 00:00-00:01 EST
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
Posted on 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
Posted on Jul 21, 2025 - 16:03 EDT