> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/public/integration-paths.md).

# Integration Paths

There's no single right way to integrate with MD Integrations — the right path depends on your team, your stack, and how much control you want over the experience. Every path connects to the same physician network and leads to the same core loop: checkout, intake, physician review, prescription, and fulfillment. What changes is how much you build versus how much MDI provides out of the box.

Explore the available paths. Each option supports the same clinical workflow, with different implementation effort and control.

* [API](#api)
* [White-Label Apps](#white-label-apps)
* [Shopify](#shopify)
* [WooCommerce](#woocommerce)

## Compare your options

| Path             | Engineering effort | Launch speed | Customization              | Best for                                    |
| ---------------- | ------------------ | ------------ | -------------------------- | ------------------------------------------- |
| API              | High               | Longer       | Full                       | Teams building a bespoke patient experience |
| White-Label Apps | Medium             | Fast-Medium  | Branding and configuration | Teams prioritizing speed to launch          |
| Shopify          | Low                | Fast         | Storefront-led             | Existing Shopify brands                     |
| WooCommerce      | Low                | Fast         | Storefront-led             | Existing WooCommerce brands                 |

{% hint style="info" %}
**Quick decision:** Choose the API for complete control. Choose White-Label Apps for the fastest launch. Choose Shopify or WooCommerce when your existing store runs on that platform.
{% endhint %}

You can also mix and match integration types to unlock new opportunities. For example, use webhooks or Automations with Shopify to automate patient notifications. You can also use our APIs to build an intake form while using our white-label Patient Portal platform.

### API

The API is for teams with engineering resources who want full control. Building on the API gives you the most flexibility to design a fully custom patient experience, tailored intake flows, and deep integration with your existing product. This path asks the most of your engineering team and gives the most in return.

### White-Label Apps

White-Label Apps provide MDI's prebuilt, ready-to-use intake and messaging experience, themed with your branding. This is the fastest path to launch, with minimal engineering effort required — you're adopting an experience MDI has already built and tested and making it look like yours.

{% hint style="warning" %}
White-Label Apps still require integrating a few endpoints to connect the experience to your store-front. MDI provides all front-end experiences pre-built out of the box.
{% endhint %}

### Shopify

Shopify is for brands already selling on the platform. A plugin connects your existing storefront to MDI and our white-label apps, so patients can move from checkout into the intake and physician review flow without leaving the experience your customers already know.

### WooCommerce

WooCommerce is for brands already selling on WordPress. Like the Shopify path, a plugin bridges your storefront to MDI, letting you add telehealth to an existing WooCommerce store with minimal disruption.

## How to think about it

If you have engineering capacity and want a fully bespoke experience, the API gives you the most room to build. If you want to move quickly with little to no engineering lift, White-Label Apps get you there fastest. If you're already running on Shopify or WooCommerce, the corresponding plugin is usually the simplest way to add telehealth to a storefront you've already built.

Many partners start with a faster path and move to a deeper integration later — the underlying platform is the same either way.

{% hint style="success" %}
You can launch with White-Label Apps or a storefront plugin, then move to the API later. Your patient and fulfillment workflows remain on the same underlying platform.
{% endhint %}

## Before you begin

* **API:** Confirm your team can build checkout, intake, and patient-facing workflows.
* **White-Label Apps:** Prepare your brand assets and decide which experience settings you need.
* **Shopify or WooCommerce:** Confirm your storefront is live and products are ready for telehealth checkout.

Step-by-step setup guides for each of these paths, including implementation details and technical requirements, are available in the partner documentation once you register.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mdintegrations.com/public/integration-paths.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.