> For the complete documentation index, see [llms.txt](https://ideonapi.gitbook.io/enrollment/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/enrollment/implementation-resources/frequently-asked-questions/coverage-periods/complete-setup.md).

# Complete Setup

This page contains some common questions and answers about using the Complete Setup endpoint.

`/coverage_periods/{id}/complete_setup`

### ***Q. When should the***** `complete_setup` *****call be used, and why is this required?***

*A.*  This request is what kicks-off the first task in our operations workflow and allows you to communicate that your work to load a group is completed. This means Ideon's Operations team can begin work!

You can call this:

* **Before** you create `qualifying_life_events` to enable us to start early workflow tasks, or 
* **After**, to indicate that all information has been provided for a given coverage period.  

During implementation, the Ideon team will work with you to determine what is best for your system. 

### ***Q. Should we call this endpoint when we add new coverage period, or add plans to an existing coverage period?***

A. We expect a Complete Setup call per new coverage period. If you create a new coverage period for the purpose of Renewal, or more than one per group due to multiple Carriers, please POST a call to this endpoint to alert us of each coverage period.

For one Group, with two coverage periods across a given plan year, we would expect to have one **call per coverage period (2 calls total)** to the complete setup endpoint. 

### ***Q. Can we call this endpoint multiple times? Are there any errors or restrictions?***

  A. There are no restrictions to calling this endpoint multiple times. Conversely, there is no benefit once the first call has succeeded. 

Our system saves the first time this request is called and uses that to enable the first workflow Task for our Operations team. 

If that action has already occurred, nothing would be triggered by subsequent Complete Setup requests, nor would any errors occur.