Google Fit REST
The Google Fit REST API enables you to store and access health and wellness data in the fitness store from apps on any platform. You can manage data sources, datasets, sessions, and aggregate fitness data for activities like steps, heart rate, sleep, and workouts.
Google Fit REST publishes 1 API on the APIs.io network: Users API. Tagged areas include Activity Tracking, Fitness, Google, Health, and Sessions.
The Google Fit REST catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.
Google Fit REST’s developer surface includes authentication, getting-started guide, pricing, and 5 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Google Fit REST Users API
The Users API from Google Fit REST — 6 operation(s) for users.
Open Collections 3
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONGoogle Fit REST API
OPEN COLLECTIONGoogle Fit REST Users API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Google Fitness Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Google Fitness Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Fitness Context
JSON-LDSpectral Rules 2
Spectral governance rulesets for linting and validating these APIs.
Google Fit REST API Rules
SPECTRALGoogle Fit REST API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions for this provider's data models.
Google Fit Session
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Source (apis.yml)
Work with this as data
Every provider 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 providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/google-fitness"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/google-fitness/operations?limit=25"
curl "https://apis.io/api/v1/providers/google-fitness/evidence"
Discovery needs no key. Ratings and market analysis are Pro.