# Google Fit REST

**Canonical:** https://apis.io/providers/google-fitness/  
**APIs profiled:** 1

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.

## Kin Score — 41.2 / 100 (developing)

Scored 2026-08-21 under rubric 0.12.0. Trend: flat (+0.5 from 40.7).

| Facet | Score |
|---|---|
| Discoverability | 68.5 |
| Contract Quality | 67.8 |
| Governance | 13.6 |
| Contract Governance | 13.6 |
| Operational Transparency | 7.9 |
| Developer Ergonomics | 23.8 |
| Commercial Clarity | 26.3 |
| Access Clarity | 26.3 |

Regulatory layer — **Health**: 50.0 (matched via tags).

## Agent readiness — 29.1 (agent-aware)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | documented |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Freemium · Self-serve signup — onboarding: self-serve, pricing: freemium, trial: no (confidence: high).

## APIs (1)

- **Google Fit REST Users API** — The Users API from Google Fit REST — 6 operation(s) for users.

## Agentic access (1)

- **Google Fitness Agentic Access** — 9 operations · 5 acting

## Security (3)

- **Google Fitness Authentication** — oauth2 · 1 scheme
- **Google Fitness Domain Security** — TLSv1.3 · HSTS · DMARC
- **Google Fitness Vulnerability Disclosure** — security.txt · contact published

## Plans (1)

- **Google Fitness Plans Pricing**

## Tags

Activity Tracking, Fitness, Google, Health, Sessions, Wearables, Wellness

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/google-fitness/). Scores are computed from the provider's own public artifacts under a published rubric.