Fitbit Web API Explorer
55
AI ReadinessFoundational (C)55/100
Official vendor OpenAPI document · agent-readyHealthcareClinical 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffitbit.com%2Ffitbit" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffitbit.com%2Ffitbit" | 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 with Jentic One, the self-hosted execution layer
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
Fitbit Web API Explorer
- Foundational (C)55/100
71
Foundational Compliance43
Developer Experience & Jentic Compatibility55
AI-Readiness & Agent Experience78
Agent Usability35
Security77
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
83%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
43
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: D-Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
20%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
55
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
70%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
98%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
53%
Summary Coverage
Coverage of summaries across operations/tags/info.
78
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A-Signals: 1
78%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
35
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
35%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
77
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
77%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Fitbit Web API by hand means running the OAuth2 flow for the right per-scope consent, refreshing tokens, and spreading calls across 122 activity, sleep, heart, and body endpoints with your own retries. Through Jentic you install once, import Fitbit from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Fitbit scopes to the consenting user's own data through the /user/-/ path and per-scope OAuth grants rather than an owned resource id you pin, so limit the agent to the operations it needs, such as reading a sleep log or logging a workout, and leave the rest out of the allowed set. You choose which operations it may call.
Credential isolation
Your Fitbit OAuth2 tokens are stored once per user, encrypted, by your own Jentic One instance and refreshed and injected into the Authorization header at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a sleep log' or 'log a workout', and Jentic returns the matching Fitbit operation with its input schema so the agent calls the right one of 122 endpoints without browsing the reference docs.
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.
Can I limit what my agent is allowed to do with the Fitbit Web API?
Yes. Because you run Jentic One yourself, you decide which of the 122 Fitbit operations your agent may call and set the rules that govern them. Fitbit scopes access to the consenting user's own data through the /user/-/ path and per-scope OAuth grants, so you can allow only what the agent needs, such as reading a sleep log from /1.2/user/-/sleep/date/{date}.json or logging a workout via /1/user/-/activities.json, and leave everything else out of the allowed set. The OAuth2 tokens stay under your control and are injected at execution time rather than exposed to the agent.
GET STARTED