OAuth 2.0 is used for authorizing the API calls. In order to access users data via the API, one needs to first receive an access token. Then this access token needs to be included either as a query parameter or in the headers.

Response:{
"access_token": "1f964f74ea84e50663cde2f2d888d60f7878b6b089c1e7274c3d44270a69aa8d",
"refresh_token": "a7c0f36d2d737b8adcb839aebbbed03943dae6375edcf77de2146fc53db4369df5532a7a989dc35b168b0eaa67c36db16ceebe9ec72fe1dbd155b0280274b61f",
"token_type": "bearer",
"userID": "1"
}
In case of a successful login, you get an access token back giving you authentication and authorization. Additionally, you get the userId which you can use in the URIs of thesubsequent API calls to the platform. You need to include this token in each and every consecutive request APIs to confirm the authentication.

This is the endpoint where a series of a particular observation type (weight for example) can be retrieved given a range. One possible usage could be to plot entries on a UI chart. Observations API endpoint retrieves user data in the FHIR format (https://www.hl7.org/fhir/). Since observations API retrieves multiple observations for a period of time, these are returned as a part of FHIR 'bundle' (https://www.hl7.org/fhir/bundle.html). The array of entries of this bundle are the (aggregated) observations for the requested period with each one being a FHIR 'observation' resource (https://www.hl7.org/fhir/observation.html).

For some observation types such as 'feeding' and 'bloodpressure' observations are also orginized in components.

2.1.1 Parameters

# 'Start' and 'end' (required)

- These are start and end dates of the period for which observations will be retrieved;
- The only accepted format is 'YYYY-MM-DDTHH:mm', for example, '2014-11-25T12:00'
- All times are in UTC