Open Wearables API

Name: Open Wearables API
Brand: Open Wearables API
Availability: InStock

✓ Official Vendor SpecHealthcareClinical DataapiKey10 EndpointsREST

For Agents

Ingest, normalize, and query wearable device health data — heart rate timeseries, workouts, sleep, plus OAuth-based provider connections — across vendors.

Install Jentic One Beta

Connect the Open Wearables API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Open Wearables API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Open Wearables API.

Create and list users in the Open Wearables tenant via /api/v1/users

Retrieve a user's connected wearable provider list with /api/v1/users/{user_id}/connections

Pull normalised timeseries health data (heart rate, steps, etc.) via /api/v1/users/{user_id}/timeseries

GET STARTED

Start building with Open Wearables API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Open Wearables API for, with concrete tasks.

★ Unified Wearable Data for Health Apps

Health and fitness apps that want to support multiple wearable brands without maintaining a separate Fitbit, Whoop, Oura, and Garmin integration each can use Open Wearables as a single backend. /api/v1/oauth/{provider}/authorize starts the per-vendor OAuth flow and stores the resulting tokens, then /api/v1/users/{user_id}/timeseries returns normalised heart rate, steps, and similar metrics. The app code talks to one schema regardless of the underlying device.

POST /api/v1/users to create a user, redirect to /api/v1/oauth/fitbit/authorize, then GET /api/v1/users/{user_id}/timeseries for the heart_rate metric

Workout Feed for Coaching Platforms

Personal training and coaching platforms can pull each athlete's workout history via /api/v1/users/{user_id}/events/workouts. The response is normalised across providers so a Whoop strain workout and a Garmin run share the same field structure (start_at, duration, distance, calories). This avoids per-vendor parsing in the coaching app and keeps the coach's dashboard consistent.

GET /api/v1/users/{user_id}/events/workouts?start=2026-06-01&end=2026-06-11 and aggregate total distance and duration

Sleep Tracking Integration

Sleep research and wellness apps can call /api/v1/users/{user_id}/events/sleep for nightly sleep sessions including duration, stages, and quality scores when the upstream provider exposes them. /api/v1/providers/{provider}/users/{user_id}/sync can be used to force a backfill if a study participant's data is stale, ensuring research timelines aren't blocked by sync gaps.

GET /api/v1/users/{user_id}/events/sleep for the last 30 nights and compute average total sleep time

AI Agent Health Coach

An AI agent acting as a health coach can use Open Wearables through Jentic to fetch a user's recent timeseries, workouts, and sleep without integrating each wearable vendor directly. Jentic supplies the X-Open-Wearables-API-Key from the vault and resolves the agent's intent ('how did I sleep last night') into the right /events/sleep call.

Through Jentic, search 'get user sleep sessions', resolve to GET /api/v1/users/{user_id}/events/sleep, and execute for the past 7 days

Key Endpoints

10 endpoints — open wearables api ingests and queries health data from wearable devices through a unified surface.

METHOD

PATH

DESCRIPTION

POST

/api/v1/users

Create a user in the Open Wearables tenant

GET

/api/v1/users/{user_id}/connections

List a user's wearable provider connections

GET

/api/v1/users/{user_id}/timeseries

Get normalised health metric timeseries

GET

/api/v1/users/{user_id}/events/workouts

List a user's workout events

GET

/api/v1/users/{user_id}/events/sleep

List a user's sleep sessions

GET

/api/v1/oauth/providers

List supported wearable providers

GET

/api/v1/oauth/{provider}/authorize

Start an OAuth flow for a provider

POST

/api/v1/providers/{provider}/users/{user_id}/sync

Trigger a fresh sync from a provider

POST

/api/v1/users

Create a user in the Open Wearables tenant

GET

/api/v1/users/{user_id}/connections

List a user's wearable provider connections

GET

/api/v1/users/{user_id}/timeseries

Get normalised health metric timeseries

GET

/api/v1/users/{user_id}/events/workouts

List a user's workout events

GET

/api/v1/users/{user_id}/events/sleep

List a user's sleep sessions

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The X-Open-Wearables-API-Key is stored encrypted in the Jentic vault. Agents call Open Wearables through Jentic without holding the key directly, and rotation can be done centrally without redeploying agent code.

Intent-based discovery

Agents search Jentic with intents like 'get user heart rate timeseries' or 'list workouts' and Jentic returns the matching Open Wearables operation with its parameter schema.

Time to first call

Direct integration with Open Wearables: half a day to wire the API key, OAuth provider redirects, and timeseries pagination. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Open Wearables API through Jentic.

What authentication does the Open Wearables API use?

Open Wearables uses an API key passed in the X-Open-Wearables-API-Key header. Through Jentic the key is stored encrypted in the vault and injected at request time, so the raw value never enters the agent's prompt or logs.

Can I pull heart rate data for a specific time window with the Open Wearables API?

Yes — GET /api/v1/users/{user_id}/timeseries accepts metric, start, and end query parameters. Specify metric=heart_rate and the desired window to get back normalised samples regardless of which upstream provider supplied the raw data.

What are the rate limits for the Open Wearables API?

Open Wearables enforces tenant-level rate limits documented at docs.openwearables.io. Limits scale with plan; bulk syncs should use POST /api/v1/providers/{provider}/users/{user_id}/sync rather than tight polling on /timeseries to stay within the budget.

How do I connect a user's Fitbit through Jentic?

Search Jentic for 'connect a wearable provider', load the GET /api/v1/oauth/{provider}/authorize schema, and execute with provider=fitbit and the user_id. Jentic returns the redirect URL the user follows to complete the upstream OAuth handshake.

Which wearable brands does the Open Wearables API support?

Call GET /api/v1/oauth/providers for the live list. Open Wearables typically supports Fitbit, Whoop, Oura, Garmin, and similar consumer wearables; the providers endpoint is the source of truth because the list evolves.

How do I trigger a backfill of a user's data from their wearable?

POST /api/v1/providers/{provider}/users/{user_id}/sync forces a fresh pull from the upstream provider for that user. Useful when a study or coaching window requires complete historical data rather than the default ongoing sync.

Open Wearables API

Connect the Open Wearables API to your agent

Capabilities

Start building with Open Wearables API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs