canonical: https://jentic.com/apis/twinehealth.com/twinehealth

# Twinehealth Fitbit Plus API

Overview The Fitbit Plus API is a RESTful API. The requests and responses are formated according to the [JSON API](http://jsonapi.org/format/1.0/) specification. In addition to this documentation, we also provide an [OpenAPI](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md) "yaml" file describing the API: [Fitbit Plus API Specification](swagger.yaml). Authentication Authen. The API exposes 62 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create action, get an action. Covers 62 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Create action
- Get an action
- Update an action
- Query and filter Fitbit Plus API records by parameters
- Monitor Fitbit Plus API operational status and events

## Use cases

### Storage and Databases Operations

Use the Fitbit Plus API to perform storage operations programmatically. The API provides 62 endpoints covering core functionality including create action, get an action, update an action.

Example prompt: Call POST /action to create action

### Automated oauth Management

Automate oauth operations by combining multiple Fitbit Plus API endpoints. Agents can get an action and then update an action in a single workflow.

Example prompt: Call GET `/action/{id}` to get an action, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Fitbit Plus API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'create action', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/action` | Create action |
| GET | `/action/{id}` | Get an action |
| PATCH | `/action/{id}` | Update an action |
| POST | `/bundle` | Create bundle |
| GET | `/bundle/{id}` | Get a bundle |
| PATCH | `/bundle/{id}` | Update a bundle |
| POST | `/calendar_event` | Create calendar event |
| GET | `/calendar_event` | List calendar events |

## Key resources

- **oauth** — Authentication operations
- **organization** — An organization is a Fitbit Plus customer. No data is accessible across organizations.
- **group** — A group is a cohort of patients within an organization. The creation of groups allows for the segmen
- **coach** — A coach is a person that supports a patient
- **reward program** — A reward program provides the details for a rewards program for a group. Different rewards programs

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the Fitbit Plus API use?

The Fitbit Plus API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create action with the Fitbit Plus API?

Yes. Use the POST /action endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Fitbit Plus API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create action through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create action'. Jentic returns the matching Fitbit Plus API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Fitbit Plus API have?

The Fitbit Plus API exposes 62 endpoints covering oauth, organization, group operations.

### Can I limit what my agent is allowed to do with the Fitbit Plus API?

Yes. Jentic One is self-hosted, so your own rules decide which Fitbit Plus API operations and credentials the agent may use. Because the resource id sits in the URL path, you can pin the agent to reads on a specific action or bundle with GET `/action/{id}` or GET `/bundle/{id}`, and the OAuth2 scopes further bound access to a single group or organization. Writes such as POST /bundle or PATCH `/bundle/{id}` are excluded unless you explicitly add them.