Oura
Oura is a health-technology company that makes the Oura Ring — a titanium smart ring packed with PPG, body-temperature, SpO2, and motion sensors — and the Oura App and Oura Cloud platform that turn raw biometrics into daily Sleep, Activity, Readiness, Stress, and Resilience scores. The Oura Developer Cloud exposes a v2 REST API and webhook subscriptions over OAuth 2.0 and Personal Access Tokens, letting third-party applications read 50+ health metrics, raw heart-rate and interbeat-interval time series, sleep stages, workouts, sessions, user-authored tags, and ring telemetry. A parallel /v2/sandbox/usercollection/* surface provides deterministic sample data for integration testing.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Oura the way a machine reads it — 64 machine-readable artifacts across 22 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 — Oura scores 62.1/100 (strong), with a separate agent-readiness read of 54/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 Oura
Each block below is one kind of artifact we hold for Oura. 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 22
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.
Oura Daily Activity Routes API
The Daily Activity Routes API from Oura — 2 operation(s) for daily activity routes.
Oura Daily Cardiovascular Age Routes API
The Daily Cardiovascular Age Routes API from Oura — 2 operation(s) for daily cardiovascular age routes.
Oura Daily Readiness Routes API
The Daily Readiness Routes API from Oura — 2 operation(s) for daily readiness routes.
Oura Daily Resilience Routes API
The Daily Resilience Routes API from Oura — 2 operation(s) for daily resilience routes.
Oura Daily Sleep Routes API
The Daily Sleep Routes API from Oura — 2 operation(s) for daily sleep routes.
Oura Daily Spo2 Routes API
The Daily Spo2 Routes API from Oura — 2 operation(s) for daily spo2 routes.
Oura Daily Stress Routes API
The Daily Stress Routes API from Oura — 2 operation(s) for daily stress routes.
Oura Enhanced Tag Routes API
The Enhanced Tag Routes API from Oura — 2 operation(s) for enhanced tag routes.
Oura Heart Rate Routes API
The Heart Rate Routes API from Oura — 1 operation(s) for heart rate routes.
Oura Interbeat Interval Routes API
The Interbeat Interval Routes API from Oura — 1 operation(s) for interbeat interval routes.
Oura Personal Info Routes API
The Personal Info Routes API from Oura — 1 operation(s) for personal info routes.
Oura Rest Mode Period Routes API
The Rest Mode Period Routes API from Oura — 2 operation(s) for rest mode period routes.
Oura Ring Battery Level Routes API
The Ring Battery Level Routes API from Oura — 1 operation(s) for ring battery level routes.
Oura Ring Configuration Routes API
The Ring Configuration Routes API from Oura — 2 operation(s) for ring configuration routes.
Oura Sandbox Routes API
The Sandbox Routes API from Oura — 35 operation(s) for sandbox routes.
Oura Session Routes API
The Session Routes API from Oura — 2 operation(s) for session routes.
Oura Sleep Routes API
The Sleep Routes API from Oura — 2 operation(s) for sleep routes.
Oura Sleep Time Routes API
The Sleep Time Routes API from Oura — 2 operation(s) for sleep time routes.
Oura Tag Routes API
The Tag Routes API from Oura — 2 operation(s) for tag routes.
Oura VO2 Max Routes API
The VO2 Max Routes API from Oura — 2 operation(s) for vo2 max routes.
Oura Webhook Subscription Routes API
The Webhook Subscription Routes API from Oura — 3 operation(s) for webhook subscription routes.
Oura Workout Routes API
The Workout Routes API from Oura — 2 operation(s) for workout routes.
Scroll within the panel for all 22 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Oura API
OPEN COLLECTIONGraphQL 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.
Pricing 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.
Rate 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.
Oura Ring 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.
Oura Ring Finops
FINOPSFeatures 24
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 24 ·
Semantic 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.
Oura Ring Context
JSON-LDSpectral Rules 2
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.
Oura API Rules
SPECTRALOura API Rules
SPECTRALJSON Schema 3
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.
Examples 3
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.
Oura Daily Activity Example
EXAMPLEOura Daily Sleep Example
EXAMPLESecurity Posture 3
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.
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 Oura — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/oura-ring · machine-readable index on apis.io