Skip to content
Helpdesk & ticketing

twinehealth.com

Fitbit Plus sandbox and mock 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 Au Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
62
Collections
-
Event types
-
Start this simulation
example request
curl https://your-twinehealth.slurry.io/pub/calendar_event \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version v7.78.1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 62.

  • POST/action
  • GET/action/{id}
  • PATCH/action/{id}
  • POST/bundle
  • GET/bundle/{id}
  • PATCH/bundle/{id}
  • GET/calendar_event
  • POST/calendar_event
  • GET/calendar_event/{id}
  • PATCH/calendar_event/{id}
  • DELETE/calendar_event/{id}
  • POST/calendar_event_response