Fitbit · GraphQL Specification

Fitbit GraphQL Schema

Conceptual GraphQL schema for the Fitbit Web API — a wearable health and fitness platform acquired by Google in January 2021 and now part of Google's hardware portfolio alongside Pixel Watch. The legacy Fitbit Web API is scheduled for deprecation in September 2026; new integrations should target the [Google Health API](https://developers.google.com/health).

Documentation Endpoint View on GitHub WearableHealthFitnessActivity TrackingHeart RateSleepGoogleIoTGraphQL

Overview

Fitbit GraphQL Schema is a GraphQL API specification published by Fitbit on the APIs.io network.

Conceptual GraphQL schema for the Fitbit Web API — a wearable health and fitness platform acquired by Google in January 2021 and now part of Google’s hardware portfolio alongside Pixel Watch. The legacy Fitbit Web API is scheduled for deprecation in September 2026; new integrations should target the Google Health API.

Tagged areas include Wearable, Health, Fitness, Activity Tracking, and Heart Rate.

Endpoint

Related API Specs

Fitbit User API (OpenAPI) Fitbit Foods API (OpenAPI) Fitbit Oauth2 API (OpenAPI)
Back to Fitbit · All GraphQL Specs · GitHub

Work with this as data

Every GraphQL schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for graphql

4 MCP tools reach this
  • find_graphqlBrowse and filter every GraphQL schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This GraphQL schema
curl "https://apis.io/api/v1/graphql/fitbit-graphql"
All graphql
curl "https://apis.io/api/v1/graphql?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.