Skip to main content
One API that carries a patient from your checkout through licensed clinical review, fulfillment, and every refill after. OpenLoop runs the regulated clinical layer; you keep your funnel, your design, and your customer relationship.
No. Selling care normally means becoming a healthcare company first: licensing, clinical review, pharmacy, fulfillment. OpenLoop makes that unnecessary and handles everything that needs a license behind your brand.
OAuth 2.0 client credentials (machine-to-machine). Exchange your client_id / client_secret at POST /v0.1/auth/token for a short-lived Bearer access token, then send it as Authorization: Bearer <access_token> on every request. Credentials come from your OpenLoop implementation contact. See API Overview → Authentication.
Mostly synchronous. You start the journey with a few calls and read patients, questionnaires, subscriptions and invoices back; order status and per-medication tracking are not a read: they arrive as prescription webhook events to an HTTPS endpoint you register with OpenLoop (configured per customer, not self-serve). See Order status and tracking and Prescription events.
Enroll the patient and submit the program intake, take payment with a checkout session, then read status. Licensed review begins once the intake lands. The Partner Cookbook walks the whole journey in order with the exact calls and responses.
Weight management, sexual health and hair. Programs are configurable service lines — see Programs and identifiers for how to read what your tenant has, and check availability for a patient’s state via the API.
None for the /v0.1 surface yet — call the API over HTTP. The API Reference carries the exact requests and responses, including auth, pagination and idempotency.
Start with the Quickstart: from sandbox credentials to an approved test consult in about fifteen minutes. Your implementation contact provides sandbox and production credentials.