Fitbit Web API Explorer
✓ Official Vendor SpecHealthcareClinical Dataoauth2122 EndpointsREST
For Agents
Read consented activity, sleep, heart rate, body, and intraday time-series data for Fitbit users, and log activity, sleep, weight, or food entries on their behalf.
Use for: Get the step count and active zone minutes for the user yesterday, Retrieve the sleep log for the last 7 nights, Find the user's current cardio fitness score, I want to pull intraday heart rate at one-minute resolution
Not supported: Does not handle medical-grade diagnostics, EHR record exchange, or non-Fitbit wearable data — use for consented Fitbit user activity, sleep, heart, body, and intraday data only.
The Fitbit Web API exposes consented user health and activity data captured by Fitbit wearables, the Aria scale, and manual logs. The 122 endpoints cover activity, heart rate, sleep, body composition, breathing rate, ECG, cardio fitness (VO2 Max), temperature, irregular rhythm notifications, foods, friends, devices, and intraday time-series data at minute or second resolution. Authorization is OAuth 2.0 with per-scope user consent, suitable for digital health apps, employer wellness programmes, and research studies.
Install Jentic One Beta
Connect the Fitbit Web API Explorer to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fitbit Web API Explorer, 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.
1
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 | sh2
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 instanceJentic 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 Fitbit Web API Explorer API.
Read daily activity summaries, steps, distance, and active zone minutes from /1/user/-/activities endpoints
Pull intraday heart-rate and active-zone-minute series at minute or second granularity
Retrieve sleep logs, sleep goals, and sleep stages over date ranges
Access body weight, fat percentage, BMI, and Aria scale measurements over time
Surface clinical-grade signals — ECG readings, VO2 Max scores, temperature, breathing rate, and HRV intraday
Manage subscriptions to receive webhooks when a user's activity, body, or sleep data changes
Log activity, food, water, weight, or sleep entries on behalf of a consented user
Use Cases
Patterns agents use Fitbit Web API Explorer API for, with concrete tasks.
★ Digital Health Research
Pull consented intraday data — heart rate at one-minute resolution, breathing rate, HRV, and ECG readings — for participants in remote studies. The Fitbit Web API is one of the few consumer wearables APIs that exposes this depth of physiological data, suitable for IRB-approved research and digital therapeutics. Most studies have data ingestion live within a week.
GET /1/user/-/activities/heart/date/2026-06-09/1d/1min.json for participant X to pull one-minute heart rate, then sync to the study database
Wellness and Coaching Apps
Surface daily activity summaries, sleep quality, and active zone minutes inside a coaching or insurance wellness app. The /1/user/-/activities/date/{date}.json endpoint returns one consolidated day-summary object that is easy to render. Subscribe to data changes via the subscriptions endpoints so the app updates without polling.
Pull /1/user/-/activities/date/today.json and present steps, active zone minutes, and resting heart rate in a wellness card
Cardiac Risk Monitoring
Retrieve ECG readings, irregular rhythm notifications, cardio fitness (VO2 Max) scores, and HRV intraday data to feed a cardiac risk model or alerting workflow. Useful for digital health platforms and employer health programmes that surface flagged readings to a clinician for review. Live in 1-2 weeks including consent flows.
Query the irregular rhythm notifications endpoint, then for any positive notification pull the corresponding ECG reading and forward it to the clinician dashboard
AI Agent Health Operations
Use Fitbit through Jentic so a wellness agent can answer 'how did I sleep last night?' or log a workout via natural language. Jentic exposes the 122 endpoints as discoverable tools, with the OAuth2 access token in the vault. Get started at https://app.jentic.com/sign-up
Through Jentic, search 'get sleep log for last night', load the /1.2/user/-/sleep/date/{date}.json schema, and execute with date=yesterday
Key Endpoints
122 endpoints — the fitbit web api exposes consented user health and activity data captured by fitbit wearables, the aria scale, and manual logs.
METHOD
PATH
DESCRIPTION
GET
/1/user/-/activities/date/{date}.json
Daily activity summary
GET
/1.2/user/-/sleep/date/{date}.json
Sleep log for a date
GET
/1/user/-/activities/heart/date/{date}/1d/{detail-level}.json
Intraday heart rate
POST
/1/user/-/activities.json
Log an activity
POST
/1.2/user/-/sleep.json
Log a sleep entry
GET
/1/user/-/devices.json
List connected Fitbit devices
POST
/1.1/oauth2/introspect
Introspect an OAuth 2.0 token
GET
/1/user/-/activities/date/{date}.json
Daily activity summary
GET
/1.2/user/-/sleep/date/{date}.json
Sleep log for a date
GET
/1/user/-/activities/heart/date/{date}/1d/{detail-level}.json
Intraday heart rate
POST
/1/user/-/activities.json
Log an activity
POST
/1.2/user/-/sleep.json
Log a sleep entry
GET
/1/user/-/devices.json
List connected Fitbit devices
POST
/1.1/oauth2/introspect
Introspect an OAuth 2.0 token
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Fitbit OAuth2 access and refresh tokens are stored encrypted in the Jentic vault per end user. Token refresh and Authorization header injection happen at execution time, so the agent only ever sees scoped data not raw tokens.
Intent-based discovery
Agents search by intent (e.g. 'get sleep log' or 'log a workout') and Jentic returns the matching Fitbit operation with its input schema, removing the need to navigate 122 endpoints across activity, sleep, heart, and body domains.
Time to first call
Direct Fitbit integration: 1-2 weeks for OAuth, scope handling, token refresh, and rate-limit back-off across endpoints. Through Jentic: under 1 hour for the API surface — OAuth consent capture remains your responsibility.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Fitbit Web API Explorer API through Jentic.
What authentication does the Fitbit Web API use?
Fitbit uses OAuth 2.0 with per-scope user consent (activity, heartrate, sleep, weight, etc.). Through Jentic, the access token and refresh token are held in the encrypted vault and the Authorization header is injected at execution time.
Can I get intraday heart rate with the Fitbit Web API?
Yes. Endpoints under /1/user/-/activities/heart/date/{date}/1d/{detail-level}.json return intraday heart rate at 1sec, 1min, 5min, or 15min granularity, subject to Fitbit approving your application for intraday access.
What are the rate limits for the Fitbit Web API?
Fitbit applies a default limit of 150 API calls per hour per user per app. The response includes Fitbit-Rate-Limit-Remaining and Retry-After headers. Higher limits require an application review.
How do I pull a sleep log through Jentic?
Search Jentic for 'get sleep log for a date', load the /1.2/user/-/sleep/date/{date}.json schema, and execute with the user's date. The response includes total minutes asleep, stages (deep, light, REM, wake), and per-stage durations.
Can the Fitbit Web API push events instead of polling?
Yes. Use the Subscriptions API (/1/user/-/{collection}/apiSubscriptions/{subscriptionId}.json) to register your endpoint; Fitbit will POST a notification when the user's activities, body, sleep, or food data changes, so you fetch only on update.
Does the Fitbit Web API expose ECG and irregular rhythm data?
Yes. ECG readings and Irregular Rhythm Notifications are exposed as separate tagged endpoints under the user namespace, suitable for cardiac risk dashboards once the user grants the appropriate scope.
GET STARTED