Menu

Fitbit Web API returns 410 Gone: how to keep sleep, HRV and weight flowing into intervals.icu
📰

Fitbit Web API returns 410 Gone: how to keep sleep, HRV and weight flowing into intervals.icu

DEV Community: api·antivex·17 days ago
#2A3G8O7k
#devtoapi#devto#dev#health#google
Long article (1057 words) — no AI summary yet.
Reading 0:00
15s threshold

On 2 November 2026 Google turned off the legacy Fitbit Web API. If a script, app or sync tool that fed your Fitbit data into intervals.icu stopped working this week, this is the most likely reason. Here is what changed, how to recognise it, and the routes that still work, with their real limits.

What changed

Google's developer page for the Google Health API gives the timeline:

30 September 2026: support for the legacy Fitbit Web API ended.

2 November 2026: the Fitbit Web API and the Fitbit OAuth endpoints were turned off. Requests to them now fail with HTTP 410 Gone .

The replacement is the Google Health API ( health.googleapis.com ), with new OAuth scopes and new data types.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.