# FAQs | Question | Answer | | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | How do I know what plans are available? | Use the [QuoteConnect API](/api-reference/endpoints/quoteconnect-api.md) (`POST /api/v1/quotes`) to get available plans for a member. Each plan includes `deeplink_enrollment` and `api_enrollment` flags indicating which enrollment paths it supports. You can also look up a single plan with `GET /api/v1/plans/:hios_id`. | | How do I know if a plan supports EnrollConnect or Deeplink? | Every plan returned by QuoteConnect includes `api_enrollment` and `deeplink_enrollment` boolean flags. Use `api_enrollment: true` for EnrollConnect, `deeplink_enrollment: true` for Deeplink. See [Enrollment Decision Path](/integration-guide/enrollment-decision-path.md) for routing logic. | | What is the difference between EnrollConnect and Deeplink? | **EnrollConnect** gives you full API control over the enrollment lifecycle: create, update, validate, submit, cancel, and terminate applications programmatically. **Deeplink** redirects the user into the HealthSherpa UI to complete enrollment. Both accept the same canonical application schema. Use EnrollConnect when you want to keep the user in your platform; use Deeplink when the carrier or plan does not yet support `api_enrollment`. | | How do I reconcile enrollments? | **EnrollConnect**: Every application has an `application_id` returned at creation. Use `GET /api/v1/applications/:id` to check status at any time, or subscribe to [Webhooks](/api-reference/webhooks-api.md) for real-time updates. You can also pass an `external_id` in the application request for your own reference. **Deeplink**: Pass an `external_id` parameter in the deeplink URL. Subscribe to webhooks or download enrollment exports to reconcile. | | What happens if an application is accidentally duplicated? | **EnrollConnect**: Your platform controls application creation, so you can check for existing applications before creating new ones. **Deeplink**: Duplicate submissions can occur. Agents or administrators can review previous submissions in the HealthSherpa dashboard before submitting. | | Do premium payments occur in-flow? | For carriers that support it, the `GET /applications/:id` response includes `payment_instructions` indicating whether payment is required with submission, whether a redirect URL is available, or whether the carrier accepts phone payments. In-flow payment via `payment_method` in the application request is a planned enhancement. | | What if a member requests a plan change or resubmission? | **EnrollConnect**: Use `PUT /api/v1/applications/:id` to update an existing draft application before submission. After submission, cancel the application (`POST /cancel`) and create a new one. **Deeplink**: Changes to submitted applications must be made through the HealthSherpa dashboard. | | Do I need a separate login for each person completing an application? | **EnrollConnect**: No. API authentication uses an `x-api-key` header, not individual user accounts. **Deeplink**: No. Authentication is not required for enrollment submissions. | | What attestation text do I need to show? | Use `GET /api/v1/plans/:hios_id?include=enrollment_requirements` to retrieve carrier- and state-specific attestation content. Display the `content` values in your UI and pass the corresponding fields in the application request. See the Plan Lookup section of the [QuoteConnect API](/api-reference/endpoints/quoteconnect-api.md) for details. | | What does the `%{signature_name}` placeholder mean? | Some attestation text (specifically `electronic_signature_consent`) contains `%{signature_name}`. Replace this with the applicant's full legal name before displaying the text. All other placeholders (carrier name, etc.) are resolved server-side. | | What is `_agent_id`? | The `_agent_id` is an optional identifier tied to an agent's login in the HealthSherpa UI. When provided, the application appears under that agent's dashboard. This is separate from the `agent_of_record` fields used for commissions and carrier submissions. If your platform does not use HealthSherpa agent accounts, you can omit this field. | --- # 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/integration-guide/faqs.md?ask= ``` 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.