Accessing Demo Data in the API

To help you get started quickly with Human API, we provide a demo data set that is similar to what you will get from a user. This demo data is based on anonymous personal data that we’ve collected.

We provide a demo token that allows you to query the API directly from your application without having to onboard real users or authenticate real data sources. Any stream that is currently available can be queried and the data will change over time (just like it would with a real user).

To start playing with demo data just use demo as a token instead of a real access token like so:

As a Bearer Token:

-H "Authorization: Bearer demo" https://api.humanapi.co/v1/human

Filtering Demo Data by Source

If you would like to see a payload returned from a specific source, you can use the source query parameter like so:

"https://api.humanapi.co/v1/human/medical/encounters&source=54dc427aaa6b4cb7d6203028"
// this is an example--does not return data

Simulate medical authentication end-to-end

Although you can use the demo token as described above to pull demo data from our servers, in order to see the end-to-end authentication flow you must log in with user credentials in Connect.

We make fictional accounts accessible just like any other account. Follow these steps to connect a fictional account

1. Launch Connect
2. When you are prompted to search for a data source, search for Starfleet Medical or Starfleet Pharma.
3. Use demouser and password as the login credentials

The fictional accounts will have the following datatypes:

• Allergies
• Functional Statuses
• Immunizations
• Instructions
• Demographics
• Plans of Care
• Procedures
• Profile
• Encounters
• Medications
• Narratives
• Problems
• Test Results
• Vitals
• Social History
• Reports
• CCDs

For more information about these datatypes, please visit our medical API reference.

🚧

How about demo Wellness accounts?

Human API does not maintain demo accounts with Wellness sources such as Fitbit. Please connect your own accounts in order to test end-to-end authentication.

Simulate errors when authenticating medical sources

Authentication by a medical user in Connect may not always be successful due to a variety of factors. This includes action required in the source medical portal, inaccessibility of the source CCD files, an outage at the source portal, etc.

To help simulate those scenarios, we have specific demo user credentials that you can use for testing. See below for more information: