# Sunfire Integration Data Mapping

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

**Purpose:** Explains what data is sent between <code class="expression">space.vars.Kizen\_company\_name</code> and SunFire and when that data is exchanged during quoting and enrollment.
{% endhint %}

## Overview

This page describes how data is exchanged between <code class="expression">space.vars.Kizen\_company\_name</code> and SunFire during a SunFire session and completed enrollment. When SunFire is launched from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>, <code class="expression">space.vars.Kizen\_company\_name</code> sends required demographic information to pre-fill the quote or enrollment experience.

Once the session and enrollment are complete, SunFire returns enrollment and session details back to <code class="expression">space.vars.Kizen\_company\_name</code>. This data exchange helps keep <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entities</code> up to date, supports accurate <code class="expression">space.vars.entity</code> matching, and ensures enrollment information is captured consistently across both systems.

When data is sent vs returned:

* Data is sent from <code class="expression">space.vars.Kizen\_company\_name</code> to SunFire when a user launches SunFire from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>. This data is used to pre-fill the quoting or enrollment experience.
* Data is returned from SunFire to <code class="expression">space.vars.Kizen\_company\_name</code> after a SunFire session or enrollment is completed. Returned data includes enrollment details and selected session information, which are used to update the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> in <code class="expression">space.vars.Kizen\_company\_name</code>.

### Data Sent from Kizen to SunFire

Data is sent from <code class="expression">space.vars.Kizen\_company\_name</code> to SunFire in two scenarios: when launching SunFire from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>, and when starting a new session (for customers with token-based authentication).

**Initial Launch**

When you launch SunFire from <code class="expression">space.vars.Kizen\_company\_name</code>, the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> must include the basic demographic fields listed below. All other fields are optional.

| Data Sent                                         | Source in Kizen                                                                                      |
| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Basic demographics (Name, Date of Birth, Address) | <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> |
| ZIP Code (required to view plans)                 | <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> |

**When Creating a New Session (Token-Auth Customers)**

For customers configured with a `crm_partner_id` and token-based authentication, <code class="expression">space.vars.Kizen\_company\_name</code> sends additional session data when the agent selects **Create new session** in the launch modal:

| Data Sent | Source in Kizen                                                                                      | Notes                                                                                                                                                                                                          |
| --------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Providers | <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> | Only the first provider address matching the <code class="expression">space.vars.contact</code>'s ZIP code is sent, to prevent duplicate doctor entries. This may not guarantee the preferred address is sent. |
| Pharmacy  | <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> | Only the most recent pharmacy from the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> is sent.                                                           |
| Drugs     | <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> | All drugs on the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> are sent.                                                                                |

{% hint style="info" %}
**Note:** If any providers, drugs, or pharmacies cannot be matched in SunFire's system, <code class="expression">space.vars.Kizen\_company\_name</code> displays a warning message identifying the unmatched records.
{% endhint %}

### **Data Returned from** SunFire **to Kizen**

<code class="expression">space.vars.Kizen\_company\_name</code> receives information from both the enrollment and session once the process is complete.

Enrollment data returned to <code class="expression">space.vars.Kizen\_company\_name</code>:

* First Name
* Last Name
* Email
* Home Phone
* Address (street, city, state, county, ZIP)
* Gender
* DOB: (mm/dd/yyyy)
* FIPS (county code)
* Medicare ID

Fields returned to <code class="expression">space.vars.Kizen\_company\_name</code> from a session include:

* Providers
* Pharmacy
* Drugs

{% hint style="info" %}
**Note:** Syncing is additive. Data added in **SunFire** is written to the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> in <code class="expression">space.vars.Kizen\_company\_name</code>, but removing data in SunFire does **not** remove it from <code class="expression">space.vars.Kizen\_company\_name</code>. To maintain a clean <code class="expression">space.vars.entity</code>, manually remove any unwanted session data in <code class="expression">space.vars.Kizen\_company\_name</code> before launching SunFire.
{% endhint %}

***

## What's Next

Next, continue to [SunFire Contact Matching Rules](/docs/integrations-and-plugins/integrations/sunfire/sunfire-contact-matching-rules.md) to understand how returned enrollment data is matched to existing <code class="expression">space.vars.contacts</code> in <code class="expression">space.vars.Kizen\_company\_name</code> and how duplicate <code class="expression">space.vars.entities</code> are prevented.

<details>

<summary>Related Topics</summary>

* [SunFire](/docs/integrations-and-plugins/integrations/sunfire.md)
* [Launching SunFire from a Contact Record](/docs/integrations-and-plugins/integrations/sunfire/launching-sunfire-from-a-contact-record.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/sunfire-integration-data-mapping.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.