- Test data
This feature is currently under development for the following providers:
- Apple Health Kit
- Freestyle Libre
The others will be coming soon. If there is a particular provider you would like us to add please do not hesitate to contact us at firstname.lastname@example.org!
When integrating with Vital, you may not own a physical device for each provider you’re planning to support. For this, we provide demo users with test data so you can build and test the whole integration without touching a real device.
A demo user gives you the same experience as using a real one, the only difference is that you won’t go through the Vital Link flow.
After creating the user, the
Users page of your dashboard will look like this:
Now you can create a demo connection for the Vital user you just created, in this case
150db84c-537c-4cad-a6e9-24dc589d7fa2. You can directly hit the API endpoint or using one of our client libraries, as shown below:
After the demo connection is created, a Fitbit logo will appear beside your user.
From here, everything works exactly the same as if you connected a real device. This means you will receive the following webhook updates:
- Connection created, as soon as the connection is created.
- Historical webhooks. We simulate historical data for the demo device and send the corresponding webhook updates, as in the real-world scenario.
- Daily webhooks. We also simulate updates to the device data every couple of hours so you can test receiving the data when a user recorded a workout or other activity.
- Refresh user data. You can also instantaneously refresh a user’s data through this endpoint.
For demo connections there will be 30 days of historic data backfilled. This is in contrast with data backfill for non demo providers, where the number of days data backfilled varies according to the provider. You can find out more here
When connecting to the live Vital client, there are three data response structures available for data. Raw, Stream and Summary
When connecting to the demo Vital client data is only available in the Summary structure.
Summary restructures provider data fields, to have a consistent response structure across all providers. This is the easiest way to use provider data across an application which connects to multiple providers.