Builders can now grant access to their data in Zus to other Builders they have formal business relationships with (e.g., business associate agreement). For example, if you are a business associate and you want your customers to use Zus as part of your service offering to them, you can use Cross-Builder Grants to manage your customers' users and patient data in Zus on their behalf.

Builders can now allow end-users of their applications to interact with Zus APIs without requiring an additional login step. For more information, see: this tutorial in our User Authentication page.

Users can now interact with APIs in the Zus sandbox outside of Postman by logging in directly through this documentation site. Please read on for more details.

Builders can now subscribe to data creation and update activity in Zus's Operational Data Store (ODS). For more information, see: https://docs.zushealth.com/docs/subscriptions.

The latest Auth Service API is now the only Auth Service API available. The legacy Auth Service API has been removed, so users can no longer interact with the legacy API by setting the Content-Type API header to application/legacy+5-9-2022.

We are excited to release the new, default Auth Service API with capabilities closely aligned with the latest JSON v1.0 API spec. Please read on for details on breaking changes and legacy Auth Service API deprecation timeline.

On April 25, 2022, Zus Health will release a new version of the Auth Service API with new capabilities more closely aligned with the latest JSON v1.0 API spec. Please read on for details on breaking changes and rollout timeline.

Zus applications and Postman now support single sign-on (SSO) with external enterprise identity providers. See below for information on the SSO experience and how to set up an SSO connection with Zus. 🙌

We are very excited to announce the launch of our payer data ingestion, medical history, and medication history APIs! More information below ✨

Builder admins can now add new users and configure their access permissions in a self-service fashion via the Zus API. This comes with an important breaking change. Details below 👇