Product

Your data, through your own keys.

A REST API and a FHIR R4 endpoint, switched on by your administrator in Settings. Generate a key, choose the scopes, and read or write against the same record the product uses.

Sign in

Off by default. An owner or administrator enables it in Settings → API access.

Where you turn it on

Settings → API access. Nobody has to open a ticket.

API access is disabled until an owner or administrator enables it, which keeps a live endpoint from existing on an account that never asked for one.

Settings · API accessHarbor Point Recovery
REST API

Read and write patients, appointments, notes, claims, and staff records.

Enabled
FHIR R4 endpoint

Standards-based read access for health information exchange and partner systems.

Enabled
Webhooks

Push events to your own systems on admission, discharge, signature, and remittance.

Disabled
Include Part 2 protected records

Off unless a qualifying consent covers the recipient. Enforced per request, not per key.

Disabled
Live key pk_live_8f2a••••••••••••••••••••4c71Scopes patients:read · appointments:read · claims:write
The API access screen in Settings, with the REST API and FHIR endpoint enabled and webhooks and Part 2 records left off.
GET /fhir/r4/Patient/hp-0041982200 OK · 84ms
# request
curl https://api.unisonahealth.com/fhir/r4/Patient/hp-0041982 \
  -H "Authorization: Bearer pk_live_8f2a…" \
  -H "Accept: application/fhir+json"

# response
{
  "resourceType": "Patient",
  "id": "hp-0041982",
  "active": true,
  "name": [{ "family": "Alvarez", "given": ["R."] }],
  "birthDate": "1991-04-17",
  "managingOrganization": { "reference": "Organization/harbor-point" },
  "meta": { "security": [{ "code": "R", "display": "restricted" }] }
}

What is exposed

FHIR R4 resources and the REST equivalents.

The FHIR endpoint is read-oriented and built for exchange. The REST API is what you use to build against your own account.

  • Patient
  • Encounter
  • Condition
  • Observation
  • MedicationRequest
  • AllergyIntolerance
  • CarePlan
  • Practitioner
  • Organization
  • Coverage
  • Appointment
  • DocumentReference
Scoped keys

Each key carries explicit scopes. A reporting key that can only read appointments cannot write a claim.

Every call is logged

API requests appear in the same immutable activity log as human access, with the key and the IP.

Part 2 is enforced

Protected records are excluded unless an active consent covers the recipient. A key cannot override that.

Rate limits

Published per-key limits with clear headers, so a bulk export does not degrade your clinicians' day.

Sandbox account

Build against synthetic data before you point anything at a live tenant.

Bulk export

Take your full record set out in a usable format at any time, including on the way out.

Why it is a setting and not a sales conversation

Your records should not be something you have to negotiate access to.

Charging for API access is a way of charging you to leave. It is a toggle, it is included, and the documentation is public once your administrator turns it on.

R4FHIR version supported

Questions

Common questions.

Does Unisona Health offer an API and FHIR access?

Yes. There is a REST API to read and write patients, appointments, notes, claims and staff records, and a FHIR R4 endpoint for standards-based read access — including Patient, Encounter, Condition, Observation, MedicationRequest, CarePlan and Coverage — for health information exchange and partner systems.

Does API access cost extra?

No. It’s a toggle in Settings → API access that an owner or administrator turns on, and the documentation is public once enabled — charging for API access is a way of charging you to leave. A bulk export of your full record set is available any time, including on the way out.

Is API access secure and Part 2 aware?

Yes. Keys carry explicit scopes (a read-appointments key can’t write a claim), every call is written to the same immutable activity log as human access, published per-key rate limits protect clinician performance, and Part 2 protected records are excluded per request unless an active consent covers the recipient — a key cannot override that. A sandbox with synthetic data lets you build before pointing at a live tenant.

Get started

Start today, or take a look first.

Create your workspace in minutes and try the whole platform free for 14 days — no credit card. Or book a one-hour walkthrough first.

Start your free trial