> 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 to Agency Connect Integrating with HealthSherpa ACA APIs HealthSherpa's Agency Connect 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. {% hint style="info" %} The documents you're reviewing are for Agency Connect, which is designed for agencies and FMOs managing integrations at scale. Access is gated, and is approved on a case-by-case basis. Please contact us if you're interested. [HealthSherpa One](https://one.healthsherpa.com) serves different integration needs. HealthSherpa One is HealthSherpa's integration platform for agents looking to improve their tooling. If you're not sure which applies to you, HealthSherpa One is the faster path to get started. {% endhint %} ## For Agencies and Agency Platforms Agency Connect gives agencies and platforms several ways to programmatically connect their systems to HealthSherpa's quoting, enrollment, and servicing workflows. Depending on your use case, you can: * Send client data into HealthSherpa ahead of an application, so agents have a reference view of information already captured in your system * Launch prefilled quote sessions for consumers with a single click from your CRM or agency platform * Match provider and prescription data to plan coverage, so agents and clients see accurate network and formulary results without re-entering that information * Pull premium estimates and plan data into your own tools to support quoting or lead qualification ahead of enrollment * Track applications and enrollments with your own client identifiers throughout the enrollment lifecycle * Reduce duplicate data entry and improve data accuracy across systems ## Supported Features Agency Connect currently supports the following: **Client Intake** Send client data from your CRM into HealthSherpa through the Intake API before an agent starts an application. That data appears in a reference sidebar during the application, so agents can copy in information instead of switching back to your system or asking the client again. The Intake API also returns deep links scoped to that specific client, so agents land directly on the plan list or application start rather than a generic entry point. **Provider and Prescription Lookup** Look up a client's doctors and medications using HealthSherpa's Provider and Rx search endpoints. Results can be passed into a deeplink so the plan list reflects coverage for that exact provider and drug list, giving agents and clients accurate network and formulary information without manual lookup. **Plan Details & APTC Estimate API** Pull premium estimates and plan-level data for a household into your own tools. This supports use cases like generating a quote preview or qualifying a lead before the client continues to HealthSherpa to select a plan and complete enrollment. **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. This identifier enables precise tracking and record matching, eliminating the need for fuzzy matching based on names, emails, or phone numbers, and 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. **Exports** Download CSV exports of client, lead, enrollment, and follow-up data from across your organization. This gives leadership a structured data feed for reporting, reconciliation, and operational oversight without needing to pull that information manually from HealthSherpa. Agencies commonly ingest export data into their own systems to tie enrollments to commissions, support advance commissioning and payout forecasting, and trigger sales, service, and retention workflows. ## Quick note regarding integration possibilities {% 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. 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. 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 * [status.healthsherpa.com](https://status.healthsherpa.com) ## Where to Start 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=&goal= ``` `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.