Enrollment Decision Path

Coming Soon — These fields are not yet live. They will appear in staging before production. Your account manager will notify you.

---

New Plan Fields

Two new boolean fields will appear on each plan in the Quoting API response:

Field	Type	Description
deeplink_enrollment	boolean	Plan supports enrollment via the Application Deeplink.
api_enrollment	boolean	Plan supports full enrollment via the EnrollConnect API.

---

Example Response

{
  "plans": [
    {
      "hios_id": "53901AZ1490005",
      "name": "Blue Portfolio HSA Gold Statewide PPO",
      "gross_premium": 450.25,
      "year": 2026,
      "deeplink_enrollment": true,
      "api_enrollment": true,
      ...
    },
    {
      "hios_id": "84271TX0100001",
      "name": "Ambetter Balanced Care 15",
      "gross_premium": 325.00,
      "year": 2026,
      "deeplink_enrollment": true,
      "api_enrollment": false,
      ...
    }
  ]
}

---

Routing Logic

┌───────────-────┐
│  POST /quotes  │
└───────┬────-───┘
        │
        ▼
┌───────────────────────────┐
│ api_enrollment = true?    │──yes──▶ EnrollConnect API
└───────────┬───────────────┘
            │ no
            ▼
┌───────────────────────────┐
│ deeplink_enrollment = true│──yes──▶ Application Deeplink
└───────────┬───────────────┘
            │ no
            ▼
    Not enrollable via
       HealthSherpa

Both the EnrollConnect API and the expanded Application Deeplink accept the same canonical request schema. Build your payload once, then route it to either endpoint based on these flags. See Choosing an Enrollment Path for details.

---

Plan Lookup

You will also be able to retrieve enrollment flags for a specific plan without running a full quote:

GET /api/v1/plans/:hios_id?plan_year=2026

Returns the same deeplink_enrollment and api_enrollment fields for a single plan:

{
  "hios_id": "53901AZ1490005",
  "name": "Blue Portfolio HSA Gold Statewide PPO",
  "year": 2026,
  "deeplink_enrollment": true,
  "api_enrollment": true,
  ...
}

This is useful when you already have a plan selected and need to confirm which enrollment path it supports before building your request.

Fast follow. This endpoint will also return an enrollment_requirements object listing required fields, conditionally required fields (with plain-language conditions), and payment/SEP metadata for the selected plan's carrier. This lets your platform know exactly what data to collect before making any enrollment API calls, rather than discovering requirements through the validation error loop.

---

Backward Compatibility

• These fields are additive. Existing integrations continue to work.

• The include_non_enrollable_offex parameter is unchanged.

• Fields can be requested via filter:

GET /api/v1/quotes?...&filter=deeplink_enrollment,api_enrollment