Deeplinks V2 API Specification

Coming Soon — This specification is in active development and subject to change. Schemas, field names, and endpoint behavior may be revised before general availability.


Overview

The Application Deeplink V2 accepts the full canonical enrollment schema — the same request body used by the EnrollConnect API. The key difference: the deeplink returns an HTTP 302 redirect to the HealthSherpa-hosted enrollment UI, where the user completes the application with all provided fields prefilled.

For migration details, structural changes from V1, and field-by-field breakdowns, see the Deeplinks V2 Guide.

The request body is the same canonical schema as the EnrollConnect API, with the addition of skip (deeplink-specific). All fields beyond the required four (plan_hios_id, plan_year, applicants.primary, residential_address) are optional — the more you prefill, the less the agent needs to complete in the HealthSherpa UI.


Base URLs

Environment
Base URL

Staging

https://staging.healthsherpa.com

Production

https://www.healthsherpa.com

Authentication uses the x-api-key header (optional in production, required in staging).


API Specification

Create prefilled application and redirect

post

Accepts the canonical application schema and redirects the user to the HealthSherpa-hosted enrollment UI with all provided fields prefilled.

This endpoint must be called from your backend. Capture the Location header from the 302 response and redirect the user's browser to it.

Authentication: x-api-key is optional in production (recommended), required in staging.

Authorizations
x-api-keystringRequired

API key provided during onboarding. Optional in production (recommended for automatic agent allow-listing), required in staging.

Body

Same canonical application schema as the EnrollConnect API, with one additional deeplink-specific field: skip.

Build your payload once — the same JSON body works for both the deeplink and the EnrollConnect API (POST /api/v1/applications).

skipbooleanOptional

Deeplink only. When true, advances the user past any steps that are already complete based on the prefilled data. When false or omitted, the user starts at the first step.

Default: false
external_idstringOptional

Your unique identifier for this application.

_agent_idstringOptional

HealthSherpa-provided agent identifier (slug).

Example: your_agent_slug
tpa_slugstringOptional

HealthSherpa-assigned TPA identifier.

plan_hios_idstringRequired

14-character HIOS plan ID.

Example: 12345AB6780001
plan_yearintegerRequiredExample: 2026
desired_effective_datestring · dateOptionalExample: 2026-01-01
american_indian_or_alaskan_native_in_householdbooleanOptional
Responses
post
/public/ichra/v2/off_ex

No content

Last updated