Fitbit Web API Explorer

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.