Human Connect is an embeddable interface for applications to allow users to share their health data with your apps and services. After a user has successfully granted you access to their health data using Human Connect, you'll be able to query their data directly from Human API.
Each user from your app, additionally, will have a unique Human API user record, which will automatically synchronize all of the user's health data from their disparate data sources.
Launch the Connect popup with two configuration parameters:
Once a user has connected their data sources and presses the "Done" button, you will receive a
sessionTokenObjectto your server.
On your server, add your unique
sessionTokenObjectand POST it to Human API's servers.
Human API will return:
publicToken. Save this data in your system with the appropriate user model.
Update your app status. You can now start using Human API for querying data.
|User ID within Human API.|
|Used to pull all data for a user.|
|Used to open the Human Connect popup for existing users.|
|Unique ID of your Human API app. Found on the app settings page of the Developer Portal.|
|Unique client secret of your Human API app. Found on the app settings page of the Developer Portal.|
|Consists of a |
Parameters with * should be stored securely with your local user model.
Finally, Connect has two modes "Create" and "Edit". Create mode is launched as described above for all user's on their first launch. Once a user connects a source you'll get a set of tokens back (step 5), one of which is the
publicToken. This token will have to be supplied to Connect on launch every subsequent time that user launches Connect to ensure proper security.
That's it! It's the same standard process regardless of the platform you launch Connect from.
Now that you've got the basics down, pick your platform below for specifics on how to add this flow to your application:
Updated over 4 years ago