WHOOP
WHOOP is a fitness and recovery wearable platform providing a REST API for accessing sleep, recovery, strain, and workout metrics from the WHOOP band. The API uses OAuth 2.0 authorization code flow with Bearer tokens to allow developers to build applications that access member health and performance data including physiological cycles, sleep stages, recovery scores, strain, heart rate, body measurements, and workout records.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles WHOOP the way a machine reads it — 55 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — WHOOP scores 52.8/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile WHOOP
Each block below is one kind of artifact we hold for WHOOP. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
WHOOP Activity ID Mapping API
Utility endpoints for activity ID mapping
WHOOP Cycle API
The Cycle API from WHOOP — 3 operation(s) for cycle.
WHOOP Partner API
Endpoints for trusted WHOOP partner operations
WHOOP Recovery API
The Recovery API from WHOOP — 2 operation(s) for recovery.
WHOOP Sleep API
The Sleep API from WHOOP — 3 operation(s) for sleep.
WHOOP User API
Endpoints for retrieving user profile and measurement data.
WHOOP Workout API
The Workout API from WHOOP — 2 operation(s) for workout.
Scroll within the panel for all 7 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
WHOOP GraphQL API
WHOOP is a fitness wearable tracking recovery, strain, and sleep. The API covers physiological metrics (HRV, resting heart rate, SpO2), recovery scores, sleep stages, workout st...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Whoop Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Whoop Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Whoop Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Whoop Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
WHOOP API Rules
SPECTRALJSON Schema 33
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ActivityIdMappingResponse
JSON SCHEMAAppointment
JSON SCHEMACreateObservationRequest
JSON SCHEMACycle
JSON SCHEMACycleScore
JSON SCHEMADiagnosticReportCreateRequest
JSON SCHEMALabRequisition
JSON SCHEMAPaginatedCycleResponse
JSON SCHEMAPaginatedSleepResponse
JSON SCHEMAPartnerTokenRequest
JSON SCHEMAPartnerTokenResponse
JSON SCHEMAPatient
JSON SCHEMAPatientCore
JSON SCHEMARecovery
JSON SCHEMARecoveryCollection
JSON SCHEMARecoveryScore
JSON SCHEMAServiceRequest
JSON SCHEMAServiceRequestStatusRequest
JSON SCHEMASleep
JSON SCHEMASleepNeeded
JSON SCHEMASleepScore
JSON SCHEMASleepStageSummary
JSON SCHEMASleepStreamDataPoint
JSON SCHEMASleepStreamResponse
JSON SCHEMAUnilabsAppointment
JSON SCHEMAUnilabsCollectionAddress
JSON SCHEMAUnilabsPatient
JSON SCHEMAUserBasicProfile
JSON SCHEMAUserBodyMeasurement
JSON SCHEMAWorkoutCollection
JSON SCHEMAWorkoutScore
JSON SCHEMAWorkoutV2
JSON SCHEMAZoneDurations
JSON SCHEMAScroll within the panel for all 33 ·
Examples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Whoop Cycle Example
EXAMPLEWhoop Recovery Example
EXAMPLEWhoop Sleep Example
EXAMPLEWhoop User Profile Example
EXAMPLEWhoop Workout Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for WHOOP — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/whoop · machine-readable index on apis.io