Introduction

​

How it is put together

• One account, one tenant. Every clinic has its own subdomain and its own isolated database. Your base URL is https://{clinic}.{region}.practicehub.io/v3/api — the host the practice signs in on (the region host is the one in the practice’s login URL — neptune (London), mercury (Frankfurt), vulcan (Ohio), jupiter (Singapore) or apollo (Sydney)) — and a credential only ever reaches the account it was created on.
• Resources, not endpoints. Each resource (patients, appointments, …) is a uniform collection: list with filters, fetch one, create, update, delete. GET /schema tells you exactly what every resource exposes and accepts.
• The app’s rules apply. Writes follow the same rules the PracticeHub app enforces — a booking checks the patient is active and the resource is at that location, a payment updates the balance, voiding an invoice releases its allocations. You get field-level validation and meaningful status codes instead of surprises.
• Your data on our records. Every record carries a metadata object for your own identifiers, which you can filter on.
• Push, not poll. Webhooks — live in a limited rollout — tell you when records change — whether the change came through the API, from staff in the app, or from a background job — with thin, signed payloads.
• Built to be discovered. The OpenAPI reference on this site is generated from the running API, and the MCP server exposes the same model to AI clients.

​

Where to next