Integrations
A signed, server-to-server API — off until someone turns it on.
Platforms and EHRs that want to submit orders programmatically use a versioned enterprise API with a documented contract.
How a partner request moves
- 1Your platformBuilds the order for one of its clinics.
- 2Signed requestTenant credential, signature, timestamp and idempotency key.
- 3TrueRoute verifiesThe credential, the signature, the time window and the key, before any work starts.
- 4Claimed onceThe key is claimed in the same transaction as the work, so a retry cannot create a second order.
Every request
What each call has to carry.
Its safe default is absent — in every environment, production included. It is switched on deliberately for a deployment, and until it is, its routes answer as though they were never written.
- A service credential scoped to one tenantThe clinic an order belongs to comes from the credential, never from the request body.
- A signature over the raw bytesAn HMAC over exactly what was sent, so a request altered in transit is refused.
- A timestamp inside a five-minute windowA captured request cannot be replayed later.
- An idempotency keyClaimed in the same transaction as the work, so a retried request cannot create a second order.
Integration inquiry
Tell us what you are building.
Credentials are issued per tenant after a conversation, not from a signup page. Tell us about your platform and the clinics on it, and someone on our team will reply.
Integration inquiry
Fields marked optional can be left blank.
No patient information, please. These forms are for business enquiries only — do not include patient names, dates of birth or prescription details.