Once you've registered your client it's easy to start requesting data from iHealth.
All endpoints are only accessible via https and are located at api.iHealthLabs.com:8443.

The URL examples throughout this documentation include an access_token that represents YOUR account tied to a generic iHealth client. DO NOT use this access_token in production or for anything other than testing as they will change often. For your application, you should have each user go through an authentication and authorization flow in order to receive a valid access_token.

Be nice. If you're sending too many requests too quickly, we'll send back a 503 error code (server unavailable).
You are limited to 5000 requests per hour per access_token or client_id overall. Practically, this means you should (when possible) authenticate users so that limits are well outside the reach of a given user.

Unit
OpenAPI V2 server also provides unit-converting function for developers. By importing the corresponding parameters, developers can get the data with different unit base. Developers can also procure data with the unit pre-defined by the users according to users’ preferences. (see appendix)

Response Type
To make it more convenient and compatible, iHealth OpenAPI V2 provides one formats of response data type(JSON)