Skip to main content
OpenLoop Partners API - the clinical backend for consumer health

The clinical backend for consumer health

Selling care usually means becoming a healthcare company first: licensing, clinical review, pharmacy, and fulfillment. OpenLoop removes that requirement. One API carries a patient from your checkout through licensed clinical review, fulfillment, and every refill after, while you keep control of your funnel, your design, and your customer relationship. We run the regulated clinical layer behind consumer health programs in weight management, sexual health, hair, sleep, and dermatology. You own the experience. We handle everything that needs a license.

The journey is seven stages, and you build them in order

You do not orchestrate the clinical workflow. You start it, then read what happened.
1

1 · Start here

Exchange your credentials for a token on staging, then run five calls that confirm your tenant is provisioned before you write any integration code.
2

2 · Intake

Create the patient and submit the program intake. The platform creates the clinical encounter and routes it to a licensed clinician.
3

3 · Payment

Create a checkout session for a price in your catalogue. Paying is what creates the order.
4

4 · Status and tracking

Order status and tracking arrive as signed prescription webhook events (prescription.created, prescription.ordered, prescription.shipped, prescription.cancelled), delivered to an HTTPS endpoint you give OpenLoop; there is no partner order read. See the Partner Cookbook.
5

5 · Scheduling

Offer availability and book visits where the program needs one.
6

6 · Refills

A refill is a questionnaire, and an approved one becomes a new order.
7

7 · Growth

Cross-sell at checkout, upgrade a subscription, and retain rather than cancel.
The Partner Cookbook walks all seven stages with the exact calls and responses, and the checks that keep them true against staging — and through the pages for when one of them goes wrong.

Built for developers

One canonical spec

Every endpoint is generated from one OpenAPI specification. Build against the reference; there are no SDKs for the /v0.1 surface yet.

Agent-ready

An MCP server exposes the same surface to AI agents, so you can build automated integrations against the platform.

Get started

Quick Start

Get a token and make your first five calls against staging

Partner Cookbook

The seven stages in order, verified against staging, with recipes for when things go wrong

API Reference

Explore every endpoint with interactive documentation and examples

Best Practices

Error handling, data validation, and status-reading patterns

Talk to us

Reach the developer support team at developer-support@openloophealth.com