Getting Started With Zonda

Zonda exposes a set of REST APIs to manage the core resources of the platform: organizations, patients, treatments, appointments, billing, and authentication. All APIs share the same base URL and authentication scheme.

Base API URL: https://api.zondahealth.com


Zonda // Auth API

Manages authentication and authorization for users and organizations. Use it to manage users, organization access, self-service account operations, and Personal Access Tokens (PATs).

Zonda // Organizations API

Manages organization-level configuration: plans, modules, insurers, and rosters. This is where you define what an organization offers and who belongs to it.

Zonda // Patients API

Manages patient data and care history. Provides organization-facing endpoints to create, search, and update patients, and professional-facing endpoints to work with patients assigned to a professional.

Zonda // Management API

Manages organization treatments and appointments. Includes both organization-level endpoints and professional-facing endpoints for treatments, appointments, and professional connections.

Zonda // Billing API

Manages settlement configuration for billing: settlement policies and policy versions, professional groups, and geographic zones used to calculate settlements.


Authentication

All API calls must be authenticated with a Personal Access Token (PAT).

Getting a PAT

  1. Log in to the Zonda platform with an admin account — only admins can create tokens.
  2. Open the Configuration panel.
  3. Create a new Personal Access Token and copy it. Tokens are prefixed with zpat_ (e.g. zpat_a1b2c3...).

⚠️

Store the token securely. Treat it like a password — anyone with the token can call the API on behalf of your organization.

Using the token

Pass the token in the Authorization header as a Bearer token:

Authorization: Bearer zpat_xxxxxxxxxxxxxxxx

Example

curl https://api.zondahealth.com/v1/patients \
  -H "Authorization: Bearer zpat_xxxxxxxxxxxxxxxx"

If the token is missing, invalid, or expired, the API returns 401 Unauthorized.