> ## Documentation Index
> Fetch the complete documentation index at: https://openloop.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Whether the integration is event-driven today, how the token exchange works, what the happy path is, which programs are live, and why there are no SDKs yet.

> [accordion] What is the OpenLoop Partners API?
>
> 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.

> [accordion] Do I need to become a healthcare company?
>
> 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.

> [accordion] How does authentication work?
>
> 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](https://openloop.mintlify.site/api-reference/introduction.md#authentication).

> [accordion] Is the integration synchronous or event-driven?
>
> 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](https://openloop.mintlify.site/cookbook/order-status-and-tracking.md) and [Prescription events](https://openloop.mintlify.site/cookbook/prescription-events.md).

> [accordion] What's the happy path?
>
> 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](https://openloop.mintlify.site/cookbook/index.md) walks the whole journey in order with the exact calls and responses.

> [accordion] What programs and verticals are supported?
>
> Weight management, sexual health and hair. Programs are configurable service lines — see [Programs and identifiers](https://openloop.mintlify.site/cookbook/programs-and-identifiers.md) for how to read what your tenant has, and check availability for a patient's state via the API.

> [accordion] What SDKs are available?
>
> None for the `/v0.1` surface yet — call the API over HTTP. The [API Reference](https://openloop.mintlify.site/api-reference/introduction.md) carries the exact requests and responses, including auth, pagination and idempotency.

> [accordion] How do I get started?
>
> Start with the [Quickstart](https://openloop.mintlify.site/quickstart.md): from sandbox credentials to an approved test consult in about fifteen minutes. Your implementation contact provides sandbox and production credentials.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.