> For the complete documentation index, see [llms.txt](https://docs.healthsherpa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.healthsherpa.com/on-exchange-api-documentation/getting-started/readme.md).

# Introduction

HealthSherpa integrations enable you to connect your CRM or agency platform directly to the ACA quoting and enrollment workflows your agents use every day. These docs will help you quickly build reliable, production-ready integrations.

## For Agencies and Agency Platforms <a href="#where-to-start" id="where-to-start"></a>

The deeplinking API empowers agencies and platforms to programmatically:

* Launch prefilled quote sessions for consumers with a single click from your CRM or agency platform
* Track applications and enrollments with your own client identifiers throughout the enrollment lifecycle
* Maintain unified workflows between your systems and HealthSherpa with seamless navigation
* Reduce duplicate data entry and improve data accuracy across systems

By integrating with HealthSherpa, agencies and platforms avoid building complex enrollment infrastructure and instead leverage a single, CMS-trusted connection to streamline the quoting and enrollment process. This reduces agent training time, minimizes data entry errors, and enables better tracking of the customer journey from lead through enrollment.

## Supported Features

The deeplinking integration currently supports:

#### Prefilled Quote Sessions

Generate personalized HealthSherpa quote sessions based on consumer data already captured in your system. Deeplinks can prefill household information, income details, zip code, and individual member characteristics including age, tobacco use, gender, pregnancy status, and ICHRA/HRA information. This eliminates the need for agents to manually re-enter information and ensures quotes are built on accurate data from your system of record.

#### Client Identifier Tracking

Pass your own unique identifier (`external_id`) for each consumer or household through the deeplink. This identifier enables precise tracking and record matching, eliminating the need for fuzzy matching based on names, emails, or phone numbers. Your identifier can be used to associate HealthSherpa activity with your internal systems for reporting and analytics.

#### Flexible Workflow Control

Control how much of the quoting process agents need to complete by using parameters like 'skip' to advance directly to plan results when sufficient information has been prefilled. This flexibility allows you to optimize the agent experience based on the completeness of data in your system.

## Quick note regarding integration possibilities <a href="#use-cases" id="use-cases"></a>

{% hint style="info" %}
If you are coming from Medicare, it is natural to expect a very deep integration; on ACA, the possibilities are quite different. Medicare and ACA integrations are regulated differently because the underlying data ownership and oversight are different.&#x20;

In ACA, the Marketplace is the authoritative source, and CMS closely controls the handling and downstream sharing of Marketplace data to prevent unauthorized use or distribution. In Medicare, the ecosystem often supports broader system-to-system exchange as a standard operating model.&#x20;

Practically, that means ACA integrations with HealthSherpa can be powerful, but they will not mirror the depth or breadth of a typical Medicare integration.

The result is that ACA integrations tend to prioritize initiating work in HealthSherpa and improving client workflow efficiency, rather than sending large volumes of consumer or application data into external systems.
{% endhint %}

## Sign up for HealthSherpa platform status notifications <a href="#sign-up-for-healthsherpa-platform-status-notifications" id="sign-up-for-healthsherpa-platform-status-notifications"></a>

* [status.healthsherpa.com](https://status.healthsherpa.com)

## Where to Start <a href="#where-to-start" id="where-to-start"></a>

We recommend beginning with the Use Cases section, where you’ll find clear examples designed to help your team integrate with confidence. Start with the use cases most agencies rely on—prefilled quoting and export data.


---

# 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.healthsherpa.com/on-exchange-api-documentation/getting-started/readme.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.