See your clinical product work before you sign anything
The sandbox is the full Lithos API with simulated providers. Your team builds the real integration, from intake to prescription to pharmacy order, and sees exactly how care will run inside your product.
- The same API and webhooks as production
- Simulated provider decisions on every encounter
- Free, with no contract and no call required
The fastest way to know if Lithos fits
See it before you sign
Most clinical platforms ask for a contract and a setup fee before you see anything. Here you see the real API, the data and the events first, and decide with evidence.
Build while the paperwork moves
Your engineers build the integration while protocols, states and the BAA are being settled, so launch day isn’t waiting on code.
Show your team the whole journey
Walk your team through intake, provider review, prescription and pharmacy inside your own product, before anything is live.
From a new patient to a filled order, in your first hour
This is the path most teams run first. Every step is a real API call or a signed webhook, the same ones you’ll use in production.
- 0:05Create a patientName, date of birth, address and the consent your app captured.
POST /v1/patients - 0:10Submit an encounterAn initial visit with your intake answers, validated field by field.
POST /v1/encounters - 0:12A provider reviews itA simulated review approves, declines or asks for more information.
← encounter.approved - 0:15A prescription is writtenMedication, dosing, quantity and days of supply, with the prescriber on record.
GET /v1/encounters/{id} - 0:20The pharmacy order movesPending, processing, completed, each one a signed webhook to your app.
← order.completed
// webhook: your app hears about every step
POST https://your-app.com/webhooks/lithos
X-Lithos-Event-Type: encounter.approved
X-Lithos-Signature: t=1791474280,v1=5f2b…
{
"id": "evt_test_9a1c",
"type": "encounter.approved",
"created_at": "2026-10-08T15:12:04Z",
"resource_id": "enc_test_51b0"
}// 0:05 · create a patient
POST /v1/patients
{
"external_id": "usr_1042",
"first_name": "Jordan",
"last_name": "Rivera"
}
// → 201
{ "id": "pat_test_8f2a" }// 0:10 · submit an encounter
POST /v1/encounters
{
"patient_id": "pat_test_8f2a",
"type": "initial",
"intake_data": { … }
}
// → 201
{ "id": "enc_test_51b0", "status": "pending_review" }// 0:12 · webhook to your app
POST https://your-app.com/webhooks/lithos
X-Lithos-Event-Type: encounter.approved
{
"id": "evt_test_9a1c",
"type": "encounter.approved",
"resource_id": "enc_test_51b0"
}// 0:15 · read the prescription
GET /v1/encounters/enc_test_51b0
// → 200
{
"status": "approved",
"prescription": {
"medication": "Semaglutide 0.25 mg",
"days_supply": 28
}
}// 0:20 · the order is filled
POST https://your-app.com/webhooks/lithos
X-Lithos-Event-Type: order.completed
{
"id": "evt_test_b7d4",
"type": "order.completed",
"resource_id": "ord_test_2c18"
}What’s the same, and what’s simulated
| Sandbox | Production | |
|---|---|---|
| API and webhooks | Identical | Identical |
| Provider decisions | Simulated, in seconds | Licensed providers in the patient’s state |
| Prescriptions and pharmacy | Simulated, nothing is sent | Sent to your pharmacy or ours |
| Patients | Test data only | Your real patients |
| Cost | Free | Per completed visit |
Three steps to your first patient
Request access
Tell us who you are. The sandbox link arrives in your inbox right away.
Build the flow
Sign up, get keys, and run the whole journey from intake to pharmacy order. Hand the docs to your coding agent if you like.
Go live
Book a call to choose protocols, pharmacy and states. Your code carries over; we commit to a launch date on that call.
Is the sandbox really free?
Yes. There is no charge and no contract. You pay per completed visit only once you go live with real patients.
Do I need to talk to sales first?
No. The link arrives by email and you can start building right away. Many teams book a short walkthrough too, so we can map the sandbox to their program.
What is simulated and what is real?
The API, data model and webhooks are the same as production. Provider decisions are simulated, and no real patients, prescriptions or pharmacy orders are created.
How much is there to build?
The API itself is small: patients, encounters, prescriptions, orders and webhooks. Most of the work is your own intake and checkout, which you control.
Can my coding agent build the integration?
Yes. The docs are one file with every endpoint, webhook and field, written so Claude Code and similar tools can read them.
What happens when we’re ready to go live?
Book a call. We choose protocols, pharmacy and states with you, sign the BAA and MSA, and commit to a launch date. Your code carries over.
Ready to see it on your program?
Get sandbox access and start building today, or book a call and we'll walk you through it.