# Overview

> The features below are in active development and will be available to integrating partners as each is released. Details are subject to change.

***

HealthSherpa is expanding its ICHRA API platform with new capabilities that give partners deeper control over the enrollment experience. Whether you need full programmatic lifecycle management, richer deeplink pre-fill, or a unified payments integration, the tools below are designed to meet you where your product is today and grow with it.

Everything described here is in active development and will be available for beta partners in the near future. Previews are subject to change, your account manager will confirm availability for each milestone.

***

### Expanded Deeplink API

The Application Deeplink is getting a major expansion. Today it supports a subset of application fields. V2 will accept the **full canonical enrollment schema**, matching the schema of the EnrollConnect API.

#### What's New

<table><thead><tr><th width="253.03338623046875">Category</th><th>New Fields</th></tr></thead><tbody><tr><td><strong>Attestations</strong></td><td>Issuer, broker, electronic signature consent, disclosure, pediatric dental</td></tr><tr><td><strong>Signatures</strong></td><td>Primary, spouse signatures and dates</td></tr><tr><td><strong>Communication preferences</strong></td><td>Notification method, marketing consent, HSA opt-in</td></tr><tr><td><strong>Guardian</strong> </td><td>Address, phone, email</td></tr><tr><td><strong>Responsible party</strong></td><td>Name, address, relationship</td></tr><tr><td><strong>Translator</strong></td><td>Name, reason, signature</td></tr><tr><td><strong>Agent of record</strong> </td><td>Address, fax, carrier producer code, signature</td></tr><tr><td><strong>Employer</strong> </td><td>Contact details, FEIN, FIPS code</td></tr><tr><td><strong>Applicant fields</strong></td><td>Student status, disability, Medicare/Medicaid eligibility, immigration, incarceration, tobacco N/A</td></tr><tr><td><strong>Dependent fields</strong></td><td>Alternate address, expanded relationships (parent, stepparent), ITIN, per-dependent email/phone</td></tr></tbody></table>

#### Why It Matters

* **More prefill:** pre-populate attestations, signatures, and payment so agents spend less time in the HealthSherpa UI.
* **One schema, two paths:** the same JSON payload works for both the deeplink and the EnrollConnect API. Build once, route to either.
* **Easier migration:** start with the deeplink, move to the full API later without changing your payload.

#### Backward Compatible

Existing deeplink parameters continue to work unchanged. V2 fields are additive.

```
             ┌─────────────────────────────────-─┐
             │    Canonical Application Schema   │
             │         (same JSON body)          │
             └──────────────┬─────────────────-──┘
                            │
              ┌─────────────┴─────────────────┐
              │                               │
              ▼                               ▼
 ┌─────────────────────────┐   ┌─────────────────────────┐
 │   Deeplink V2           │   │   EnrollConnect API     │
 │   POST /public/ichra/   │   │   POST /api/v1/         │
 │   off_ex                │   │   applications          │
 │                         │   │                         │
 │   → 302 redirect        │   │   → 201 JSON (draft)    │
 │   → User completes in   │   │   → Full lifecycle      │
 │     HealthSherpa UI     │   │     control             │
 └─────────────────────────┘   └─────────────────────────┘
```

***

### Release Timeline

<table><thead><tr><th width="276.13336181640625">Milestone</th><th width="140.86663818359375">Target</th><th>Details</th></tr></thead><tbody><tr><td><strong>EnrollConnect API + Enrollment Decision Path</strong></td><td>April 13</td><td>Core API lifecycle (create, update, submit, cancel, terminate), inline validation, enrollment flags on the Quoting API, and plan lookup</td></tr><tr><td><strong>Carrier support (staggered)</strong></td><td>Ongoing</td><td>Carriers will be enabled incrementally after launch. Your account manager will share the carrier availability schedule</td></tr><tr><td><strong>EnrollConnect enhancements</strong></td><td>April – ongoing</td><td>Support for creating incomplete applications, ability to pass payment information, and more</td></tr><tr><td><strong>Deeplinks V2</strong></td><td>May 2026</td><td>Full canonical schema support for deeplink pre-fill, backward compatible with existing integrations</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.ichra.healthsherpa.com/coming-soon/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.