Integrate with "Fitbit Plus API" from twinehealth.com in no time with Mockoon's ready to use mock sample
Start working with "Fitbit Plus API" right away by using this ready-to-use mock sample. API mocking can greatly speed up your application development by removing all the tedious tasks or issues: API key provisioning, account creation, unplanned downtime, etc.
It also helps reduce your dependency on third-party APIs and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
The Fitbit Plus API is a RESTful API. The requests and responses are formated according to the
JSON API specification.
In addition to this documentation, we also provide an
OpenAPI "yaml" file describing the API:
Fitbit Plus API Specification.
Authentication for the Fitbit Plus API is based on the
OAuth 2.0 Authorization Framework. Fitbit Plus currently supports grant
types of clientcredentials and refreshtoken.
See POST /oauth/token for details on the request and response formats.
We will provide customers with unique client credentials for each application/integration they build, allowing us
to enforce appropriate access controls and monitor API usage.
The client credentials will be scoped to the organization, and allow full access to all patients and related data
within that organization.
These credentials are appropriate for creating an integration that does one of the following:
synchronizing data with another system (such as an EMR)
The API credentials and oauth flows we currently support are not well suited for creating a user-facing
application that allows a user (patient, coach, or admin) to login and have access to data which is appropriate to
that specific user. It is possible to build such an application, but it is not possible to use Fitbit Plus as a
federated identity provider. You would need to have a separate means of verifying a user's identity. We do not
currently support the required password-based oauth flow to make this possible.
The Fitbit Plus API supports two different pagination strategies for GET collection endpoints.
Skip-based paging uses the query parameters page[size] and page[number] to specify the max number of resources returned and the page number. We default to skip-based paging if there are no page parameters. The response will include a links object containing links to the first, last, prev, and next pages of data.
If the contents of the collection change while you are iterating through the collection, you will see duplicate or missing documents. For example, if you are iterating through the calenderevent resource via GET /pub/calendarevent?sort=startat&page[size]=50&page[number]=1, and a new calendarevent is created that has a startat value before the first calendarevent, when you fetch the next page at GET /pub/calendarevent?sort=startat&page[size]=50&page[number]=2, the first entry in the second response will be a duplicate of the last entry in the first response.
Cursor-based paging uses the query parameters page[limit] and page[after] to specify the max number of entries returned and identify where to begin the next page. Add page[limit] to the parameters to use cursor-based paging. The response will include a links object containing a link to the next page of data, if the next page exists.
Cursor-based paging is not subject to duplication if new resources are added to the collection. For example, if you are iterating through the calenderevent resource via GET /pub/calendarevent?sort=startat&page[limit]=50, and a new calendarevent is created that has a startat value before the first calendarevent, you will not see a duplicate entry when you fetch the next page at GET /pub/calendarevent?sort=startat&page[limit]=50&page[after]= .
We encourage the use of cursor-based paging for performance reasons.
In either form of paging, you can determine whether any resources were missed by comparing the number of fetched resources against meta.count. Set page[size] or page[limit] to 0 to get only the count.
It is not valid to mix the two strategies.