Will Nutrition Data Sync After Fitbit API Shutdown?
Data sent through Fitbit Web APIs may stop syncing after support ends unless an app migrates or offers another route. Here’s how to identify and test your connection.
- Data sent through Fitbit Web APIs may stop syncing after support ends on October 30, 2026, unless the partner app migrates or offers another route.
- Google says this API change does not affect connections through Health Connect or Apple Health. That does not guarantee every app or metric will sync.
- Google says records already synced to a Google Health account will not be deleted because of the change; that assurance does not cover every partner app’s history.
- Identify the source, route, and destination for each metric, then test whether a timestamped entry arrives.
Will my nutrition wearable data still sync after the Fitbit API shutdown?
It depends on the route. If an app sends data through Fitbit Web APIs and has no replacement route, new data transfer may stop after support ends on October 30, 2026. Google says connections through Health Connect or Apple Health are not affected by this API change. Neither statement confirms that every app supports every field. The notice also does not establish that syncing between a Fitbit device and Fitbit’s own app will stop.
Know the source, route, and destination
For each kind of data, the source is the app where it is recorded, the route is the service that carries it, and the destination is the app or account where you want to see it. A food-log app may be the source of meals and water, while a wearable’s companion app may be the source of sleep or activity data. Those records can travel by different routes and end up in different destinations.
Fitbit Web APIs are a route that partner apps have used to exchange data with Fitbit services. Google’s announcement describes Google Health APIs, formerly known as Fitbit APIs, as a partner connection route. Google Health is the Google service or account where supported health records may appear; it is not another name for Health Connect. Health Connect is an Android layer that lets participating apps share health data. Apple Health serves a similar role on Apple devices. A source app, route, and destination must each support the specific data field for it to arrive.
Route and outcome: what to check
| Route or setup | What the change means | What to do |
|---|---|---|
| Fitbit Web APIs | Google says support ends October 30, 2026. New transfers may stop if the partner app has not migrated or provided another route. | Ask the app provider whether it has migrated and which fields it will continue to send. |
| Health Connect | Google says this route is not affected by the Fitbit Web API change. Support for a route does not mean every app shares every metric. | Check app participation, permissions, and the exact fields available in the destination. |
| Apple Health | Google says this route is not affected by the Fitbit Web API change. Individual apps still determine which data they share. | Check sharing settings in the source app and Apple Health, then verify the field in the destination. |
| Fitbit device to Fitbit’s own app | The API notice concerns third-party connections. It does not establish that Fitbit’s own device-to-app syncing will stop. | Check Fitbit’s current guidance for details about its own app syncing. |
Health Connect supports nutrition data types, including energy and nutrient fields, and a hydration record for water volume. That describes fields apps can potentially use; it does not prove a particular wearable or food-log app writes them. Google lists devices such as Oura, Apple Watch, Garmin, Samsung Galaxy watches, and WHOOP among those that can connect through Health Connect or Apple Health, while noting that available metrics vary by device and app. A compatibility listing is not confirmation that your specific meal, hydration, sleep, or activity records will transfer.
Test each data path before the change
Do not rely on a combined dashboard or an old entry as proof that current data is arriving. Test each source-to-destination path separately:
- List the source and destination for each metric. Record which app holds your food log, water entries, sleep, and activity data, and where you expect each item to appear.
- Find the active route. Check the source app’s connected-services or data-sharing settings. Identify whether it uses Fitbit Web APIs, Health Connect, Apple Health, or another route. If the app does not name the route, ask its provider rather than guessing from a device compatibility list.
- Check permissions by field. Confirm that the source app can share the relevant categories and that the destination can receive them. A general “connected” status may not mean that nutrition and hydration are enabled.
- Make a test entry where practical. Record a clearly identifiable meal or water entry and note its date and time. For wearable data, use a recent record with a visible timestamp if you cannot create a test measurement.
- Verify the same item in the destination. Match its field and timestamp. If it does not appear, check the route and permissions again, then contact the provider. If the route is Fitbit Web APIs or remains unclear, ask: “Have you migrated away from Fitbit Web APIs, and which food, hydration, sleep, and activity fields will you continue to send, through which route?”
For example, if you log meals in MyFitnessPal and use a ring app for sleep, test those as separate paths. Google lists MyFitnessPal nutrition and hydration data among information displayed in Google Health, but this does not mean the ring app supplies those records or that every field is available. A successful test confirms that the particular item transferred; it does not guarantee all historical records or future entries will transfer.
What happens to existing records and exports?
Google says records already synced to a Google Health account will not be deleted because of the API change. This assurance is limited to records already in that account. It does not guarantee that a partner app will keep sending new entries, or that the partner app’s own history is stored in Google Health.
Google’s announcement describes Google Takeout as an export option. Do not assume a Takeout export contains every partner-app record or every nutrition field. Check the export contents, and preserve important records in the app where you originally created them. Reconnecting an app also may not import its complete history; check the provider’s instructions if you need older records.
What to do now
- Map each metric to its source app, transfer route, and destination.
- Test recent food, hydration, and wearable entries, and confirm the matching fields and timestamps.
- If an app uses Fitbit Web APIs, ask whether it has migrated and which fields it will continue to send.
- Save important records in their original apps and inspect any export before relying on it as a complete backup.
Frequently asked questions
Does a listed compatible device send every metric?
No. Compatibility with Health Connect or Apple Health does not prove that an app shares every supported field. Check the source app’s permissions and verify recent entries in the destination.
Does the API change mean my Fitbit device will stop syncing to Fitbit’s app?
The notice concerns Fitbit Web APIs and affected third-party connections. It does not establish that syncing between a Fitbit device and Fitbit’s own app will stop. Check Fitbit’s current guidance for that setup.