Detecting password expiration in password-based connections (July 2025)

The Link Password Provider endpoint, the Get User Connections endpoint and the Provider Connection Error events would now report password expiration using the provider_password_expired error type.

This mainly affects Abbott LibreView patient-based connections.

Introducing Universal Group By Support to Horizon AI Query (June 2025)

Horizon AI Query is in closed beta.

Interested in the Horizon AI Query? Get in touch with your Customer Success Manager.

Horizon AI Query can now group and aggregate the data by any Table Column expression and/or any Source Column expression.

This gives you more options on how the data should be dissected — not just by calendar units, but now also by Data Source fields and categorical values from the data itself.

Details

Introducing Timeseries Data Support to Continuous Query (June 2025)

Horizon AI Query is in closed beta.

Interested in the Horizon AI Query? Get in touch with your Customer Success Manager.

We have expanded Continuous Query to support timeseries resources in addition to the previously available summary resources.

With a few simple configuration steps, Continuous Query enables you to:

  1. Extract aggregations of high‑volume timeseries data collected across all your active user device connections; and

  2. Offload this concern to Junction, allowing you to simplify your data pipeline and focus on extracting actionable signals.

Details

External User ID of User Connections (April 2025)

We now expose the External User ID of User Connections in the Provider Connection Created event and Get User Connections endpoint.

The External User ID is the unique user identifier supplied by the provider, e.g., the Fitbit User ID for Fitbit connections.

Connection typeContent
OAuth ProvidersUser unique identifier; provider-specific formats
Password ProvidersUsername
Email ProvidersEmail
Junction Mobile SDK Providersnull (not available at this time)

Details

We have increased Link Token expiry from 15 minutes to 60 minutes.

We have also added an on_error=redirect Link Token option which forces any error scenario to redirect to your specified redirect_url URL, disabling any in-built error handling behaviour in the Link Widget.

Details

Extendable Historical Date Ranges (Jul 2024)

We now offer the ability to set custom historical data ranges for wearables providers, with resource-level granularity.

Details

Introspection: Historical Pull Timeline (May 2024)

The Historical Pull Introspection endpoint now reports the execution timeline of historical pulls.

Details

Team Scope Requirements (Apr 2024)

You can now tailor what scopes Vital would request from your Users using the Org Management API. This applies when your user connects to an OAuth provider which supports scopes.

Details

Reject Duplicate Connections (Apr 2024)

You can now configure your Vital Team through the Org Management API to reject duplicate wearable connections.

Details

The Link API now reports errors in terms of a predefined set of Error Types on which your application logic can depend.

Details

Understanding Resource Availability (Apr 2024)

When a user connection to a provider is established, the webhook event now includes a resource availability report of the connection.

Details

Fallback Birth Date for Heart Rate Zones (Feb 2024)

You can now set a Fallback Birth Date on a user.

Details

Grouped Timeseries (Feb 2024)

You can now get grouped timeseries data.

Details

Historical Pull Introspection (Dec 2023)

You can now introspect the status of all one-off user historical data pulls.

Details

User Resources Introspection (Dec 2023)

You can now introspect user data ingestion statistics.

Details

Vital Sign-In Token for Mobile SDKs (Nov 2023)

Vital Sign-In Token is a new, user-scoped Authentication scheme for Vital Mobile SDKs.

Details