This page contains some common questions and answers about creating and using subscribers in the API.
/groups/{id}/subscribers
Do we need to make individual calls for each subscriber and dependent to send their information?
Yes, each subscriber needs an individual call to create and to update their information.
Dependents can be created in the same request as the subscriber, or individually using the endpoint to create a Dependent.
How often should we send updates? (new subscribers, dependents, changes in existing data)
Based on what you prefer, you can send us updates in real-time, or in batches.
For carriers with a direct API connection, a change will be sent to the carrier right away.
For carriers with a file-based connection, changes will be batched into a weekly file transmission, which will also include historical information (a "full-file")
If your system does send batch transmissions, be mindful of holding changes or events until the batch. If you receive more than one change or event for the member, you will need to preserve the order and ensure that all changes and events are processed in sequence.
Consider how the design of your integration could support or mitigate issues with "skipped" events or held events.
How can we send updates or corrections for a previously created Dependent or Subscriber?
You should send a PUT request on the subscriber or the dependent. In that request, include the elements that have changed, and required elements. You can use a GET/groups/subscribers to gather the most recent information in Ideon's system.
When we update a Subscriber or Dependent using a PUT, do we need to send a new Qualifying Life Event?
When you use a PUT to update a subscriber you don't need to send a QLE unless there is an actual life event. Many events are expressed with an update to the subscriber information (PUT/subscribers/{{id}})
If a subscriber has salary-based coverages, and the salary amounts or basis is different per coverage, How can I represent this in the Ideon API?
Ideon's API has an income_data object at the coverage level, which allows you to enumerate a different salary amount, or basis for the salary-based benefit calculation.
