Skip to main content
EMR integration guide

Healthie API integration guide: GraphQL, webhooks and Healthie Harbor

Updated
Access model
Partner program + customer API key
Developer program
Healthie Harbor
Certified FHIR access
FHIR R4 add-on (Enterprise plans)
Scheduling write
Yes, via GraphQL

The short answer

Healthie is API-first. Its GraphQL API covers appointments, clients, charting and billing, with signed webhooks for events. Third parties build through the Healthie Harbor partner program, and each customer typically requests its own API key to switch your integration on. A certified FHIR R4 API exists as an add-on for Enterprise customers.

How access works

  1. Apply to Healthie Harbor: who you are, mutual customers, what you integrate, prior EHR integrations, and HIPAA and SOC 2 status. Healthie prioritizes partners with existing customer overlap.
  2. Pass a security review and sign the partnership agreement. Fees are defined in the agreement, not published.
  3. Get documentation and sandbox credentials, build, then pass a technical review.
  4. Customers activate you by requesting an API key from Healthie for your integration.

What the APIs cover

JobPath on Healthie
Book, update, cancel appointmentsGraphQL appointment mutations
Clients, forms, charting, billingGraphQL
EventsWebhooks (HMAC-signed, retries up to 3 days, IP allowlist)
Certified FHIR readFHIR R4 add-on, Enterprise only, typical setup 4–6 weeks
Data exportONC EHI export

Your first Healthie integration, step by step

  1. Get a staging key. Generate one as described in Healthie's Authentication guide, or ask Healthie to provision it. Build against https://staging-api.gethealthie.com/graphql; production is https://api.gethealthie.com/graphql.
  2. Send the right headers. Every request is a JSON POST with Authorization: Basic <API key> and AuthorizationSource: API. Sharded organizations also need an AuthorizationShard header.
  3. Pin an API version. Healthie ships dated versions (2024-06-01 through 2026-10-01 at the time of writing) and keeps a changelog. Pin one and upgrade on purpose.
  4. Book an appointment. createAppointment needs datetime, appointment_type_id and contact_type (list valid values with the contactTypes query), plus user_id for 1:1 visits.
  5. Wire webhooks. Subscribe to appointment.created and appointment.updated. Verify the HMAC-SHA256 Signature against the Signature-Input and Content-Digest headers. Created and deleted payloads carry only the resource ID, so fetch the details over GraphQL.

Pitfalls we plan around

  • createAppointment ignores availability unless you pass enforce_availability: true. Without it, double bookings go through. Patient-side completeCheckout does enforce availability.
  • Retries are opt-in. With retries on, failed deliveries back off for up to 3 days, then the webhook is disabled. Alert on failures before that point.
  • Sub-organizations: a parent org's webhook receives events from every sub-org, so filter by organization.

Our take

GraphQL plus webhooks makes Healthie quick to build on once you're in. The gate is commercial: Harbor favors partners whose customers already ask for them. If you're early, lead with a design-partner customer on Healthie.

FAQ

Does Healthie have an API?

Yes, a versioned GraphQL API with queries, mutations, subscriptions and webhooks.

How do I become a Healthie integration partner?

Apply to Healthie Harbor, pass a security and technical review, and sign the partnership agreement. Customers then request an API key to enable your integration.

Does Healthie support FHIR?

Yes, as a certified FHIR R4 add-on for Enterprise customers, with a typical setup of 4–6 weeks.

Sources

Public pages, accessed 11 Oct and 13 Nov 2026: Healthie API docs · Become a partner · Healthie Harbor · Webhooks guide · Activating a marketplace partner · FHIR API add-on · Quick start (endpoints, headers) · Appointments guide

Other EMR integration guides

Compare every EMR we cover →
48-Hour Audit · Free

The audit is free. Another quarter of guessing is not.

Book the Free 48-Hour Audit

Integration stalled? See how we unstick it