Guides
What every integration needs to know before its first request, in the order you'll meet it.
- 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.
- Page through a list A list answers with data and a cursor. While hasMore is true, send nextCursor back as cursor for the next page.
- Stay within the rate limits Each integration client can send 600 requests a minute. Every answer says how many you have left.
- Receive and verify webhooks Practor tells your endpoint when an invoice, a claim or a payment changes. Check the signature, answer quickly, and read the invoice with your key.