Resources

Everything you need to get running.

Guides to set up your practice, developer docs for the open API, and a straight line to the team when you need a hand.

Help centre

Start with the overview.

New to AspireOS? The product overview walks through what the system does and how the pieces fit together. For anything else, the team is one message away.

Guides & templates

Set up once, run for years.

Short, practical guides for the things you’ll do in your first week.

Import your data

Bring patients, contacts and appointments across from a CSV with the guided column mapper.

Set up your fee schedule

Model your items, funding and travel rules so invoices price themselves from day one.

Working with AspireAi

How the confirm-before-act model works, and the kinds of tasks AspireAi can take off your plate.

Letter & report templates

Starting points for referrer updates and discharge summaries you can adapt to your practice.

API docs

A real open API.

Authenticate with a scoped API key. Keys are issued in Settings under AspireOS, in the Developer group — set up once and then left alone, rather than sitting between the settings you use weekly. Reach it from the Developer tools card, by searching settings for api key, or straight at /settings?tab=developers, which still resolves. A key is shown once and stored hashed, and carries read and write scopes. The base path is /api/v1, and the same pricing, EPC counting and webhook fan-out fire exactly as they do in-app.

GET /api/v1/ping read

Key check — echoes the authenticated practice.

GET /api/v1/patients read

List patients (filter by status, limit).

GET /api/v1/appointments read

List appointments (from / to / status).

GET /api/v1/invoices read

List invoices (filter by status).

POST /api/v1/appointments write

Book an appointment — prices it and fires webhooks.

POST /api/v1/intake write

Land an enquiry on the waitlist.

Webhooks

Subscribe a URL to domain events and AspireOS POSTs you signed JSON as they happen. Each body is { event, at, practice, data }, carrying an X-AspireOS-Signature header (HMAC-SHA256 of the raw body) so you can verify it before trusting the payload. Every attempt lands in an immutable delivery log. Events:

patient.created appointment.created appointment.completed invoice.paid intake.received leave.requested

Community

Built with practitioners, not just for them.

AspireOS grows out of real practice — features come from the clinicians who use it every day. Have an idea, a rough edge, or a workflow we should support? We want to hear it.