Build on Practor
Send patients and visits from your own system, bill them, and hear back when an invoice, a claim or a payment changes. REST endpoints, JSON bodies.
Start here
What every integration needs before its first request.
- Authenticate with an integration key Every request sends a key that belongs to one integration client at one practice. Here's where the key comes from and what it's allowed to do.
- Retry a create safely Every POST needs an Idempotency-Key, so a request you retry after a timeout can never create the same patient, visit or invoice twice.
- Read an error Every refusal is an RFC 9457 Problem Details body with a status that says what kind of problem it is, a code to branch on, and a list of every field to fix.
API reference
Version 1.4.0. Each page has the request to copy and every answer.
- Practitioners The practitioners of the practice, to name who saw a patient.
- Patients Register patients and keep their details matched with your system.
- Coverage A patient's medical insurance or private-pay arrangement.
- Insurance plans The medical insurance plans Practor can claim against.
- Encounters Finished visits, with their diagnoses and procedures, ready to bill.
- Invoices Invoices, the lines on them and the payments made against them.
- Claims Send an invoice's claim to the insurer, and resubmit, reverse or cancel it.
- Code systems The codes a practice bills and records with: published systems, and the practice's own, such as its tariff.
- Webhooks Events Practor sends to your endpoint when an invoice, a claim or a payment changes.
The OpenAPI document
For generating a client, or loading into your own tools.
The whole API as OpenAPI 3.1 is at /openapi.json, the same document this reference is built from. For an assistant that reads documentation, the reference is also at /llms.txt.