API sandbox
An API sandbox is a test environment that behaves like the production API — same endpoints, schemas, and webhooks — but touches no real patients, clinicians, or pharmacies, so a team can build and verify a telehealth integration end to end before anyone receives care.
- Production-identical API, no real patients
- Simulates clinician decisions and fulfillment events
- Separate keys; no data path to production
- Lithos issues sandbox credentials the same day
What a good healthcare sandbox does
Healthcare integrations fail in the states between calls — the clinician decision, the pharmacy fill, the delivery. A sandbox has to simulate those, not just accept requests.
- Separate credentials and base URL; no path from sandbox data to production
- Simulated clinician outcomes — approved, declined, needs more information — that fire real webhooks
- Simulated fulfillment: order created, shipped, delivered, with tracking
- Test patients, test catalog entries, and state variations you can trigger deliberately
- Identical request and response schemas to production, so nothing changes at launch
What to test before going live
The unhappy paths. A declined encounter, a patient whose state requires a live visit, a webhook delivered twice, a shipment that fails. Teams that test only the approve-and-ship path discover the rest with real patients. Run the full state machine in the sandbox, including your own retry and idempotency behavior, before the first production key is issued.
Compliance handled, so you can build
Lithos runs the clinicians, pharmacies, and 50-state rules behind your care program — one API.
Frequently asked questions
Does the sandbox involve real clinicians?
No. Clinician decisions are simulated so you can trigger every outcome on demand. Real clinicians review real patients only in production.
Can protected health information go in a sandbox?
It should not. Use synthetic test patients. A sandbox is a development environment and is not the place for real PHI even under a BAA.
How long does sandbox integration take?
Teams typically integrate intake and webhooks in one to two weeks and run test patients end to end before moving to production.