← Back to catalog

Support

Fitbit Plus

auto-generated
swirls add twinehealth …
actionPOSTv1.0.0

Create a patient

Create a patient record. Example for creating a patient with a group specified using `meta.query` instead of `id`: ```JSON { "data": { "type": "patient", "attributes": { "first_name": "Andrew", "last_name": "Smith" }, "relationships": { "groups": { "data": [ { "type": "group", "meta": { "query": { "organization": "58c88de7c93eb96357a87033", "name": "Patients Lead" } } } ] } } } } ```

Source
actionPOSTv1.0.0

Create a reward earning

Create a reward earning for a reward. There can only be one earning for a reward. It is possilble to create multiple reward earnings simultaneously by providing and array of reward earnings in the data property.

Source
actionPOSTv1.0.0

Create a reward earning fulfillment

Create a reward earning fulfillment for a reward earning. There can only be one fulfillment for each earning.

Source
actionPOSTv1.0.0

Create a reward program activation

Create a reward program activation for a patient. There can only be one activation for a patient for a given reward program.

Source
actionPOSTv1.0.0

Create bundle

Create a bundle in a patient's plan

Source
actionPOSTv1.0.0

Create calendar event

Create a calendar event for a patient. Attribute `all_day` must be set to `true` and `end_at` cannot be set for `plan-check-in` event type.

Source
actionPOSTv1.0.0

Create calendar event response

Create a calendar event response for an attendee of a calendar event, the attendee can be a coach or patient. Calendar event responses cannot be fetched, updated nor deleted. Use calendar event api to fetch the response status for attendees.

Source
actionGETv1.0.0

Get a bundle

Get a bundle from a patient's plan.

Source
actionGETv1.0.0

Get a coach

Get a coach record by id.

Source
actionGETv1.0.0

Get a group

Get a group record by id.

Source
actionGETv1.0.0

Get a patient

Gets a patient record by id.

Source
actionGETv1.0.0

Get a reward

Get a reward record by id.

Source
actionGETv1.0.0

Get an action

Get a health action from a patient's plan.

Source
actionGETv1.0.0

List coaches

Get a list of coaches matching the specified filters.

Source
actionGETv1.0.0

List groups

Get a list of groups matching the specified filters.

Source
actionGETv1.0.0

List reward earnings

Get a list of reward earnings matching the specified filters.

Source
actionGETv1.0.0

List reward programs

Get a list of reward programs matching the specified filters.

Source
actionGETv1.0.0

List rewards

Get a list of rewards matching the specified filters.

Source
actionPATCHv1.0.0

Update a bundle

Updte a bundle from a patient's plan.

Source
actionPATCHv1.0.0

Update a calendar event

Update a calendar event for a patient. Attribute `all_day` must be true and `end_at` cannot be specified for `plan-check-in` event type. To mark a calendar event as 'completed', set `completed_at` and `completed_by` to desired values. To mark a completed calendar event as 'not completed', set `completed_at` and `completed_by` to `null`. Attendees can be added or removed, but response status cannot be updated. Use the calendar event response api for response status updates instead.

Source
actionPATCHv1.0.0

Update a plan summary

Update a plan summary record for a patient.

Source
actionPATCHv1.0.0

Update an action

Update a health action from a patient's plan.

Source
actionPUTv1.0.0

Upsert patient

Create a new patient or update an existing patient

Source
Beyond the catalog

Any provider, on request.

01

Request it

Tell us which provider you need, and we will ship it in the registry.

02

Generate it

Point swirls add at an OpenAPI or GraphQL spec. Typed actions for any API you hold credentials for, today.

Request a providerRead the actions docs
acme · integrations
terminal
~/acme $swirls add linear
✓ 12 typed actions · scopes and schemas included
 
~/acme $swirls add https://api.acme.dev/openapi.json
◆ Fetched spec · 38 operations
✓ 6 typed actions · generated from spec