Connecting to Ideon

The Ideon Enrollment API Platform supports several means to connect.

Ideon has designed the Enrollments API Platform with your needs in mind. There are several different ways Enrollment information can be transmitted to Ideon: directly connecting to the API or transmitting files in any of the many supported flat file formats.

Connecting via the API

Getting Started

The first item you will need is an API key. Speak with your Sales representative or Integration specialist and they will set you up with two API keys, one for testing and another for production.

Ideon also supports Token-based authentication.

Build to the API

The best way to connect to the Ideon Enrollments API Platform is to directly connect to the API itself. Below is some documentation to get your team started!

Implementation Resources

Member Management

Ideon API v 0.3.3

Connecting via Flat Files

For those who do not have the time or resources to build to Ideon's API, Ideon has designed a workflow to support several standard file formats. Using this approach, you can set up your system to transmit these standard files to Ideon, and Ideon will process the data through the API and to the Carriers on your behalf.

Supported File Formats

• EDI 834

• LIMRA LDEx

• JSONL

• A few other commonly used formats – inquire for more details!

If your system generates any of the above file formats, you're already well on your way to being able to use Ideon to rapidly scale your Enrollment solution.

The Workflow

Getting Started

The first step is to build a process so you can transfer the files to an SFTP. Speak with your Sales representative or Integration specialist and they will set you up the SFTP for your team.

Transmitting Files

Ideon's system can receive files at any cadence. When your system delivers a file to the SFTP, the Ideon system will process the data into the Ideon API on your behalf, just as if you were hitting the API directly.

Reporting

Once a day, Ideon can send standard reporting files to the SFTP. These files will include the coverage counts and details that have been transmitted, as well as a standard errors file for your system or team to consume and address.