Home / Telehealth order API
Telehealth order API

Receive telehealth orders digitally — straight into fulfillment

A partner-authenticated REST API that validates, checks eligibility, routes, prices, and tracks every order automatically — with signed webhooks so your partners get real-time status.

Modern telehealth platforms don't fax scripts — they call APIs. Pharmacy Flow gives each partner a scoped API key and a single endpoint to submit orders. Every order is validated, eligibility-checked against controlled-substance and state-licensure rules, routed to the right facility, priced from the partner's rate card, and returned with a status URL.

Built for real integrations

Per-partner API keys

Each telehealth brand gets its own scoped key; partners only see and act on their own orders.

Eligibility at intake

Controlled-substance vs. ship-to-state licensure is evaluated before an order is accepted.

Idempotent

A client order id makes retries safe — duplicates return the existing order, never a second one.

Signed webhooks

order.received, held, shipped, delivered — HMAC-signed like Stripe, so partners don't have to poll.

Auto-routing

Orders route to the right facility by product family, licensure, and load.

Status API

Poll any order by number or id for live status, facility, and tracking.

How a partner integrates

Issue the partner a key, point them at the docs, and they POST orders. They receive a 201 with the order id, routed facility, and status URL — and real-time lifecycle events at their webhook endpoint. There's a live API playground inside the app to test against before going live.
The story that impresses technical buyers isn't just intake — it's the webhook callbacks. Your partner's system knows the moment an order ships, without polling. Pair it with fulfillment automation and an order flows from API call to carrier lane untouched by a coordinator.

Frequently asked questions

What does the API return?+
A 201 Created with the order id, order number, routed facility, eligibility result, and a status URL. Duplicate client order ids return the existing order (200).
How do partners get status updates?+
Two ways: poll GET /api/orders/:ref, or receive signed webhook events (order.received/held/shipped/delivered) pushed to their endpoint.
Is patient data (PHI) stored?+
The intake payload uses a partner-supplied patient reference rather than storing patient identity, minimizing PHI footprint.
Keep reading

See Pharmacy Flow on your own data

A working platform, not a slide deck. Book a walkthrough and we'll show it against your pharmacy's real workflow.