Local emulators. Real API contracts. Part of Mockingbird.
WIP Oura v2 collection and OAuth emulator for synthetic wearable synchronization tests.
Install
bun add @crvouga/mockingbird-service-oura
Usage
import { createServer } from "@crvouga/mockingbird-service-oura/server"
// Test setup: a local Oura. Its URL replaces https://api.ouraring.com in the application.
const server = await createServer({ pageSize: 2 })
const baseUrl = server.url
// Application code: the request it sends to Oura.
const response = await fetch(`${baseUrl}/v2/usercollection/workout`, {
headers: { authorization: "Bearer mock_oura_token" },
})
const { data, next_token } = await response.json()
await server.close()Run mockingbird-oura serve --port 12128; inject this origin into the consumer's API and OAuth configuration (the issue's provider strategies otherwise hard-code production). Acceptance tests use a Fetch port. bun scripts/python-smoke.ts (requires uv) additionally exercises the actual requests 2.32.5 and httpx 0.28.1 libraries over local HTTP, including token refresh and error handling; it does not exercise private consumer source.
Routes and state
POST /oauth/token accepts URL-encoded authorization code or refresh grants, Basic or body client credentials. Seed clients, codes, grants with constructor options or standard state admin routes. Default local client is mock_client / mock_client_secret; bearer mock_oura_token belongs to synthetic-user. Codes bind client, redirect, expiry and optional S256 PKCE challenge. Refresh tokens rotate once, retaining user/scopes; clock controls access expiry.
GET /oauth/authorize is the authorization endpoint a browser visits to connect a member (live: cloud.ouraring.com/oauth/authorize). There is no consent page: the request is validated, then the consents collection answers for the user and the browser is redirected (302) to redirect_uri with code and state, or error, error_description and state. The code is stored in codes bound to the client, the granted scopes, the redirect_uri when the caller sent one (the token exchange must then repeat it) and an optional S256 code_challenge (the exchange then needs the matching code_verifier); POST /oauth/token redeems it once. scope omitted grants every scope; state is optional and echoed unchanged at any length. redirect_uri may be omitted when the client has exactly one registered. An unknown client (401 invalid_client), a missing client_id, a missing or unregistered redirect_uri (400 invalid_request, JSON {status,error,error_description}) is answered in place and never redirected to. Clients take optional redirectUris (exact match; omitted accepts any absolute http(s) URI so the default mock_client works as is) and scopes (omitted allows the documented Oura scopes: email personal daily heartrate workout tag session spo2). Redirected errors: invalid_request (no response_type, or a code_challenge_method other than S256), unsupported_response_type, invalid_scope.
Consent controls: rows {id, decision: "approve"|"deny"|"error", userId?, codeTtlSeconds?, error?, errorDescription?} where id is a client id or * (every client without its own row). Seed with the consents option or POST /__admin/state/consents {"id":"*","value":{"id":"*","decision":"deny"}}. No row means approve for synthetic-user with a 600 second code. deny redirects access_denied and error redirects server_error (override with error/errorDescription), both with the unchanged state and no code. Issued codes are listed at GET /__admin/state/codes.
GET /v2/usercollection/personal_info returns the token user's personal info (id, and as seeded age, weight, height, biological_sex, email): seed a records row with collection: "personal_info", userId the token's user and data the response object (fake values only). Scope personal is required (403 {detail:"Access forbidden."} like the collections, 401 with the collections' body for an unknown or expired token, 404 {detail:"Not Found"} when the user has no row). data is returned as seeded: the email scope is not enforced per field. The default grant does not carry personal.
GET /v2/usercollection/{workout,sleep,heartrate,daily_activity,daily_spo2,daily_readiness,daily_sleep} returns {data,next_token}. Heart rate uses start_datetime/end_datetime; others use start_date/end_date against day. Fixture windows include both endpoints, omitted bounds are unbounded. These boundary/default choices are deterministic local fixture semantics, not verified live edge-case parity. Never invent an id for heart-rate samples. Fixtures retain every supplied metric, including nulls. Scope checks use workout, daily, heartrate, spo2.
Seed records rows {key,userId,collection,data}. Keys identify storage rows, not vendor ids; distinct keys can deliberately carry duplicate provider data. pageSize controls deterministic insertion-order pages. Consumers must retain the same collection/window while paginating; the emulator's row-key cursors do not bind or validate the query. No promised vendor cursor format/order. Set tokenTtlSeconds for newly issued tokens.
Test controls
Standard /__admin/health, /state, /reset, /requests, /clock, Timeline checkpoints and faults are available under /__admin (relocatable via adminPrefix). Header x-mockingbird-namespace, /__admin/ns/<name> paths and credential mappings isolate data. Journals contain metadata, never OAuth bodies or wearable payloads. Presets: unauthorized, rate_limited, server_error, connection_drop; generic faults add latency. Quota and server-error bodies are explicitly scripted fixtures, not live quota simulations. No webhooks in this surface.
Oracle and tests
Contract: official Oura OpenAPI 1.41 and OAuth documentation. Synthetic invalid credentials were checked live: token endpoint returned HTTP 400 invalid_client, collection endpoint HTTP 401 with the documented detail. Authorized collection data and refresh were not checked live.
Best guess, not oracle-verified: the authorization endpoint and personal_info are not observed live, and the vendor OpenAPI JSON was not downloadable (HTTP 404) when this was added. The parameters, the all-scopes default and the single-registered-URI default follow the Oura authentication page. The redirect status (302), the error/error_description/state redirect shape, the statuses and bodies for an unknown client or unregistered redirect_uri, the invalid_scope allow-list, S256-only PKCE, access_denied/server_error for consent controls and the 403 for a missing personal scope are the emulator's choices, not observed vendor responses. The personal_info fields (id, age, weight, height, biological_sex, email) come from the Oura v2 API documentation and third-party client documentation; whether the live response carries id is unconfirmed.
bun test runs acceptance and every-operation self-parity including divergence detection. bun run parity needs OURA_ACCESS_TOKEN, performs safe read-only envelope checks, and never prints health data or credentials.
Deliberately not modelled
No real health data, account signup, a consent page (the consents rows stand in for the user's answer), device pairing, sensor simulation, hardware SDK, webhooks, subscription lifecycle, field projection, statistical computation or full vendor metric validation. Records are synthetic pass-through fixtures; partial metrics can be seeded deliberately. Date boundary/default behavior, cursor internals and quota-body details are local stand-ins, not claims of exact vendor edge-case parity. No Python runtime dependency or claim that the private consumer itself was exercised.
API
Root runtime exports: OuraAPI, OURA_NAMESPACE, COLLECTION_SCOPES, KNOWN_SCOPES, createRuntime, OURA_PRESETS, document, operationIds, supportedOperationIds. Types include OuraAPIOptions, Grant, OAuthCode, Client, Consent, DataRecord, CollectionName, OuraRuntimeOptions, OuraRuntime, OperationId, SupportedOperationId.
/server exports createServer, serveTarget, DEFAULT_PORT and types OuraServerOptions, OuraServer.