> For the complete documentation index, see [llms.txt](https://ideonapi.gitbook.io/quote-and-select/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ideonapi.gitbook.io/quote-and-select/additional-information-and-workflows/bulk-exports-in-the-api/plan-network-mapping.md).

# Plan-Network Mapping

Export plan benefit datasets through Ideon's API

Creating a bulk export with a `type` of *plan\_network\_mappings* generates a file containing plans that are available to the user and their associated benefits. In this file, each JSON Line represents a unique plan object. The following request will generate a file with all plans that are available for quoting in the given year, product, and market.

{% code title="POST /bulk\_exports" %}

```json
{ 
    "type": "plan_network_mappings",
    "filters": {
        "year": 2026,
        "product_line": "medical",
        "market": "individual"
    }
}
```

{% endcode %}

An active license for IdeonSelect products is required to be able to export plan-network mappings; which supports the Individual Medical, Small Group Medical, and Medicare Advantage markets. Plans are unique by plan year and their plan identifier: HIOS IDs or Medicare Advantage Contract IDs. The 6-digit network identifiers are internal to Ideon.

Plan-network mapping exports return a limited set of plan identifier, network identifier, and metadata information. The truncated example below shows the information required to map a plan, unique by `id` and `year`, to a network, identified by it's `networks.id`. There will only ever be one network returned in the `networks` array.

Additionally, the `carrier` and `identifiers` objects are returned, detailing plan metadata. Documentation on these objects can be found in the Medical Grammar Guide, under the [Carrier Data](/quote-and-select/additional-information-and-workflows/benefit-grammar-guides/medical.md#carrier-and-issuer-data) and [Plan Identifiers](/quote-and-select/additional-information-and-workflows/benefit-grammar-guides/medical.md#plan-identifiers) sections.

{% code title="Truncated Sample Plan-Network Mapping JSON Line" %}

```json
{
    "id": "12345NY0000001",
    "name": "Example Plan #1",
    "year": 2026,
    "product_line": "medical",
    "audience": "individual",
    "networks": [
        {
            "id": 202721,
            "name": "UNITEDHEALTHCARE - CHOICE PLUS POS"
        }
    ],
    // .... additional carrier and plan identifier metadata
}
```

{% endcode %}

## Caching Benefits

The bulk export always returns the complete set of available plans given the filter parameters. Given this, processes to generate bulk exports to cache benefits should always fully replace data for any plans returned in previous files.

In order to deliver a seamless and performant end-user experience, we recommend caching benefits on a regular cadence using the bulk exports endpoint. This data can then be accessed more quickly in real-time to present to end users. Cached benefits can be linked by ID and year to the plan IDs returned for the real-time quote. 

We recommend configuring the cadence of exports to cache benefits based on the time of year. The cadences recommended below reflect the increased frequency of plan additions and updates when plans for the new plan year are being processed. All automated runs should be scheduled overnight (for United States time zones) in order to optimize performance. 

* September - November: daily runs, as plan inventory is being added to and updated more regularly as plans for the new plan year are being acquired and processed.
* Outside of September - November: weekly runs, as plan inventory is updated less regularly.

### Filtered Exports

It is also recommended to maintain the ability to pull a filtered plan export file on an ad hoc basis. This can be useful if users are looking to capture important plan updates or additions between automated runs. Filters can optionally be used to reduce processing time and file size for these types of runs. As an example, the following request could be used to export the individual medical plans available in NY for plan year 2026.

{% code title="POST /bulk\_exports" %}

```json
{
   "type": "plan_network_mappings",
    "filters": {
        "product_line": "medical",
        "market": "individual",
        "year": 2026,
        "states": ["NY"]
    }
}
```

{% endcode %}