Twinehealth Fitbit Plus API

Setup

Wiring the Fitbit Plus API by hand means running the OAuth2 client-credentials flow against api.twinehealth.com/pub, choosing the organization or group scope, refreshing tokens, and handling retries yourself. Through Jentic you install once, import the Fitbit Plus API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

The Fitbit Plus API puts the resource id in the URL path (/action/{id}, /bundle/{id}), so a rule can pin your agent to reads on a specific action or bundle, and its OAuth2 scopes further bound access to a group or an organization. You choose the operations it may call, so writes like creating or patching a bundle are not included unless you add them.

Credential isolation

Your Fitbit Plus API client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an action' or 'fetch a calendar event', and Jentic returns the matching Fitbit Plus API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.