Telehealth flexibilities and related extensions active through Dec 31, 2027Read the update
MyOrbitHealth

For developers · Updated 2026

Telehealth API

The MyOrbitHealth telehealth API lets your product create patients, run adaptive medical intake, route cases to a provider licensed in the patient's state, and issue prescriptions — through a REST API, signed webhooks, and a React SDK. It is HIPAA compliant with a BAA in every contract, supports EPCS e-prescribing with two-factor identity proofing, covers all 50 states across 38+ specialties, and integrates alongside an existing EHR rather than replacing it.

Become a PartnerSee the platform
Illustration of a satellite linking points on a planet

Part 01

What the API gives you

The same stack that powers our hosted clinics is exposed as a REST API with signed webhooks and a React SDK, so telehealth becomes a feature inside the product you already own.

01

Patients and consults

Create patients, open a consult, attach intake responses, and read status transitions as the case moves through provider review.

02

Adaptive intake

Submit answers to a branching clinical questionnaire and receive severity scoring and red-flag escalation rather than a flat payload.

03

Provider routing

Requests route to a provider licensed in the patient's state, load balanced across 2,400+ board-certified providers in 38+ specialties.

04

Prescriptions

Prescription events, EPCS-capable controlled-substance flows with two-factor identity proofing, and Surescripts routing to retail or compounding pharmacies.

05

Signed webhooks

Consult approved, prescription sent, order shipped, message received.

Each delivery is signed so you can verify authenticity before acting on it.

06

Video and messaging

Synchronous visits where a state requires them, plus async secure messaging, all recorded to the same auditable patient record.

Part 02

Integration patterns

Which pattern fits depends on how much of the patient experience you want to own.

Integration patterns
Full API integrationYour app owns every screen. You call the API for intake, consults, and prescriptions and react to webhooks. Most control, most engineering.
React SDK embedDrop intake and visit components into your existing front end and style them to your design system. Days of work rather than months.
Hosted clinic plus APILaunch on the hosted white-label clinic now, integrate the parts you care about later. Same stack, no replatforming.
EHR and systems integrationWebhooks plus the API let you sync consults, documents, and prescription events into an existing EHR, CRM, or data warehouse without replacing your primary system of record.
Auth and limitsBearer-token authentication, environment-scoped keys, documented rate limits, and idempotency on write endpoints. A BAA covers everything you send.

Frequently asked questions

What is a telehealth API?
A telehealth API lets a software product create patients, run medical intake, route cases to licensed providers, and issue prescriptions programmatically, instead of sending users out to a separate clinic. It is how a non-healthcare product adds real clinical capability without becoming a healthcare company.
Is the API HIPAA compliant?
Yes. Every partner signs a BAA, requests are encrypted in transit, PHI is stored encrypted in US regions, access is role based, and every read and write is logged to an audit trail. See our security page for the current control set.
Can I e-prescribe through the API?
Yes. Prescriptions are issued by the licensed provider who reviewed the case and routed through OrbitRx to a LegitScript-certified pharmacy network via Surescripts, including EPCS-capable controlled-substance flows with two-factor identity proofing. Your application never prescribes on its own.
Does it integrate with my EHR?
The API and signed webhooks let you sync consults, notes, and prescription events into an existing EHR, CRM, or warehouse. It is designed to sit alongside a primary system of record rather than replace it.
How long does integration take?
A React SDK embed is typically days. A full custom integration is usually a few weeks depending on how many verticals and states you launch and how much of the patient journey you rebuild.
Do you offer a sandbox?
Yes. Partners get environment-scoped keys so you can build against non-production data before any real patient touches the flow. Ask on the discovery call and we'll scope access with your API documentation walkthrough.

Next: API documentation, the live platform demos, and our HIPAA compliance checklist.

This page is general information, not legal or medical advice.

Build care into your product

REST endpoints, signed webhooks, a React SDK, and a licensed provider network in all 50 states.

Join now