# SunFire

{% hint style="success" %}
**Audience:** Admins, Developers, <code class="expression">space.vars.automation</code> Builders, Support & Operation teams, and Solution Architects

**Purpose:** Explains the SunFire integration in <code class="expression">space.vars.Kizen\_company\_name</code> and how it supports Medicare quoting and enrollment workflows.\`
{% endhint %}

## Overview

SunFire integrates with <code class="expression">space.vars.Kizen\_company\_name</code> to connect Medicare quoting and enrollment workflows directly to <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code>. This integration allows agents to launch quotes and enrollments from within <code class="expression">space.vars.Kizen\_company\_name</code>, with <code class="expression">space.vars.contact</code> information passed automatically between systems.

By keeping <code class="expression">space.vars.contact</code> and enrollment data aligned, the integration reduces duplicate entry, supports accurate <code class="expression">space.vars.entity</code> matching, and helps agents work more efficiently without switching between platforms.

### What is SunFire?

SunFire is a Medicare quoting and enrollment platform used by health insurance agents to compare plans, generate quotes, and submit enrollments across multiple carriers. It serves as a centralized solution for evaluating coverage options and managing the Medicare enrollment process.

SunFire is widely used in the Medicare industry to support accurate plan comparisons and streamlined enrollment <code class="expression">space.vars.workflows</code>.

***

## How does the SunFire Integration Work?

The SunFire integration allows health insurance agents (HIAs) to start a Medicare quote directly from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> in <code class="expression">space.vars.Kizen\_company\_name</code>. <code class="expression">space.vars.Kizen\_company\_name</code> automatically passes the <code class="expression">space.vars.contact</code>’s basic demographic details to SunFire, reducing manual data entry and ensuring data consistency between platforms.

Once SunFire receives the <code class="expression">space.vars.contact</code> details, the remainder of the quoting and enrollment process takes place inside the SunFire application. When the HIA completes the enrollment, SunFire sends the completed enrollment data back to <code class="expression">space.vars.Kizen\_company\_name</code> and matches it with the original <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>.

### Integration Workflow Overview

| Action                                                                                                                                                                                        | System Interaction                                                        | What Happens/Why It Matters                                                                                                                                                                                                                                                                                                                                                          |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Launch SunFire from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> in <code class="expression">space.vars.Kizen\_company\_name</code> | <code class="expression">space.vars.Kizen\_company\_name</code> → SunFire | <code class="expression">space.vars.Kizen\_company\_name</code> opens SunFire in a new browser tab and passes the <code class="expression">space.vars.contact</code>’s basic demographic information (name, date of birth, and address). This eliminates duplicate entry and prevents typos.                                                                                         |
| Complete the enrollment in SunFire                                                                                                                                                            | SunFire → <code class="expression">space.vars.Kizen\_company\_name</code> | When the enrollment is submitted, SunFire sends the enrollment details back to <code class="expression">space.vars.Kizen\_company\_name</code>. <code class="expression">space.vars.Kizen\_company\_name</code> creates a SunFire Enrollment <code class="expression">space.vars.entity</code> and links it automatically to the <code class="expression">space.vars.contact</code>. |
| Resume an existing or incomplete SunFire session                                                                                                                                              | <code class="expression">space.vars.Kizen\_company\_name</code> ↔ SunFire | <code class="expression">space.vars.Kizen\_company\_name</code> retrieves prior SunFire session data (providers/drugs/pharmacy) if the session was originally started from <code class="expression">space.vars.Kizen\_company\_name</code>. This enables the HIA to pick up where they left off without losing progress.                                                             |
| Send session data to SunFire                                                                                                                                                                  | Kizen → SunFire                                                           | When starting a new session, Kizen sends the <code class="expression">space.vars.contact</code>'s drugs, providers, and pharmacy to SunFire. This ensures SunFire has the most current <code class="expression">space.vars.contact</code> data for accurate plan matching and quoting.                                                                                               |

{% hint style="warning" %}
**Caution:** <code class="expression">space.vars.Kizen\_company\_name</code> only retrieves full SunFire session data when the quote or session was started from <code class="expression">space.vars.Kizen\_company\_name</code>. If the HIA starts a quote directly in SunFire, <code class="expression">space.vars.Kizen\_company\_name</code> retrieves only the completed enrollment, not the full session history.
{% endhint %}

***

## SunFire Requirements

To Enable SunFire on your Platform, contact [Kizen Customer Support](https://support.kizen.com/support/tickets/new).

To view plans and run quotes inside SunFire, the agent must launch the <code class="expression">space.vars.Kizen\_company\_name</code> session with a ZIP Code. SunFire uses the ZIP code to determine available plans.

**CRM Partner ID Configuration**

Certain SunFire customers require a `crm_partner_id` to be configured in the SunFire business plugin. This ID enables the token-based authentication flow used to send drug, doctor, and pharmacy data between <code class="expression">space.vars.Kizen\_company\_name</code> and SunFire on behalf of the agent.

The `crm_partner_id` is typically provisioned automatically when SunFire is enabled on your Platform.&#x20;

**Token-Based Authentication (Required for Certain Customers)**

For customers configured with a `crm_partner_id`, SunFire uses a multi-step token exchange to authenticate the agent. This allows <code class="expression">space.vars.Kizen\_company\_name</code> to act on behalf of the agent when sending or retrieving session data.

Agents must complete a one-time setup to generate their authentication code. A modal will automatically pop up the first time you launch SunFire if you have a `crm_partner_id` and are missing the CRM connect code:

1. From the <code class="expression">space.vars.Kizen\_company\_name</code> modal, follow the link to your SunFire profile page and log in if prompted.
2. Navigate to your SunFire profile and copy the authentication code.
3. In <code class="expression">space.vars.Kizen\_company\_name</code>, paste the code into the **CRM Connect Code** field on your employee <code class="expression">space.vars.entities</code> and select **SAVE**.

<div data-with-frame="true"><figure><img src="/files/mbzdTZQ8S8htKClsLABQ" alt="" width="314"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** Without a valid authentication code, agents cannot send session data (drugs, providers, pharmacy) to SunFire.
{% endhint %}

***

## Enrollments in SunFire

SunFire requires the following fields before an enrollment can be submitted:

* Address
* Gender
* Date of Birth
* Medicare Number (MBI)

If any of these are missing, the agent cannot complete and submit the enrollment.

### SunFire **Contact Matching**

SunFire uses the Medicare Number (MBI) as the primary matching field. For more information on <code class="expression">space.vars.contact</code> matching, See [Sunfire Contact Matching Rules](/docs/integrations-and-plugins/integrations/sunfire/sunfire-contact-matching-rules.md).

***

## What's Next

Next, continue to [Launching SunFire from a Contact Record](/docs/integrations-and-plugins/integrations/sunfire/launching-sunfire-from-a-contact-record.md) to learn how to start a Medicare quote or enrollment directly from a <code class="expression">space.vars.contact</code> and pass <code class="expression">space.vars.contact</code> data into SunFire automatically.

<details>

<summary>Related Topics</summary>

* [Launching SunFire from a Contact Record](/docs/integrations-and-plugins/integrations/sunfire/launching-sunfire-from-a-contact-record.md)
* [SunFire Integration Data Mapping](/docs/integrations-and-plugins/integrations/sunfire/sunfire-integration-data-mapping.md)
* [SunFire Contact Matching Rules](/docs/integrations-and-plugins/integrations/sunfire/sunfire-contact-matching-rules.md)

</details>


---

# 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://developer.kizen.com/docs/integrations-and-plugins/integrations/sunfire.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.