API

Team Brand Information is used in:

1. the Vital-hosted Link widget;
2. all user communications Vital Lab Testing sent on your behalf; and
3. the Vital-hosted Appointment Booking page for Vital Lab Testing.

Check out the Update Team and Create Team endpoint documentation.

We introduced this to provide a unified billing and administrative experience for customers having these use cases:

1. multi-region presence; or
2. user organization with diverging team-level configurations.

We introduced the Org Management API because customers have asked for the programmatic access to dyanmically create Vital Teams and manage different aspects of their Vital Teams.

Check out the Org Management API documentation.

We introduced this because this helps reduce a Vital User ID -> Client User ID database lookup on your end.

Check out the Webhook Event Structure documentation.

Before

{
  "data": {
    # ... event specific data
  },
  "event_type": "daily.data.glucose.created",
}

After

{
  "data": {
    # ... event specific data
  },
  "event_type": "daily.data.glucose.created",
  "user_id": "4a29dbc7-6db3-4c83-bfac-70a20a4be1b2",
  "client_user_id": "01HW3FSNVCHC3B2QB5N0ZAAAVG",
  "team_id": "6b74423d-0504-4470-9afb-477252ccf67a"
}

We introduced this because the user creation endpoint being idempotent can help simplify your application logic.

When the supplied client_user_id conflicts with an existing user, the 400 Bad Request response now includes the Vital User ID (user_id) and the creation date (created_on) of the conflicting user.

Check out the Create User endpoint documentation.

Check out the User Undo Deletion endpoint documentation.