TrueRoute developer docs

TrueRoute is prescription ordering and pharmacy operations software for medical spas, wellness and IV clinics and the groups that run them. The partner API lets an EHR, telehealth or practice-software product order from TrueRoute for its clinics, without the clinic leaving the software it already uses.

What you can build

1. Catalogue. Read the products and packages a clinic may prescribe, at its prices.
2. Prescribers. Sync each prescriber when it is created in your system.
3. Quote, check, order. Price a prescription, learn every reason it would be refused while the prescriber can still fix it, then submit the signed order. TrueRoute runs the same checks its own console runs and selects the route; it never re-routes silently.
4. Status. Read an order by your own id at any time (authoritative), and receive signed webhooks as it moves.
5. Labs and collection, where a clinic has them switched on: patient references keyed on your id, lab quotes and orders, results with every revision, critical values with acknowledgements, and collection appointments.

What stays with TrueRoute: pharmacy selection, pricing, the payment and its records, the prescription artifact the pharmacy receives, and the compliance checks. What stays with you: your patient chart and your prescriber's signature workflow.

Start here

• QuickstartYour first GET and your first signed POST against the sandbox.
• Authentication and signingBearer keys, the two signed forms, idempotency.
• EnvironmentsSandbox and production, and how keys decide which.
• API referenceEvery endpoint, scope and signing rule.
• WebhooksEvent types, headers and signature verification code.
• ErrorsEvery code, its category and what to do.

How access works

• One integration, many clinics. Your integration lives at one clinic (its home). Every other clinic it may act for is a grant TrueRoute records per clinic and per scope. A clinic added later reaches nothing until it is granted.
• The credential decides the clinic and the environment, never the request body. A sandbox key works only on the sandbox; a production key only on production.
• Scopes are the narrowest set your use needs (scopes).

Data you will and will not see

• Prices are clinic-facing prices. No response carries TrueRoute's cost, margin or a pharmacy's vendor codes.
• Webhooks carry ids and states only: never names, addresses, clinical text or a price breakdown. Read the order or result for detail.
• Never put a patient's identifying data in a field the contract does not define for it, in a URL, or in an Idempotency-Key.