Before you submit

Three ways to find out where a risk stands before anything is sent. None of them creates a file.

Will Valjean likely place it

POST /appetite takes the lines, the insured’s state, and either a NAICS code or a short description of the business:

{ "lines": ["GL", "LL"], "state": "SC", "naics": "722410" }

{ "lines": ["GL"], "state": "GA", "description": "garden apartments, 3 buildings" }

You get a fit (good, possible, unlikely or unknown), a plain headline, what the class will need, and how_to_send when it isn’t a good fit. A broker still reviews everything, including risks outside appetite.

What the class needs: the questions, up front

POST /requirements lists every document and answer a class of risk needs, each with a key and an answer type, so you can collect it all before you create the file:

{ "lines": ["GL"], "state": "SC", "description": "framing contractor" }

Use the same keys later on PATCH /submissions/{id}/answers.

Class guides, no key needed

GET /api/guides lists the class guides Valjean’s brokers work from (contractors, habitational, hospitality and more), and GET /api/guides/{key} returns one with every item marked required, recommended or helpful. They’re public, so a website or a form can show them.

Note

The public appetite check (/api/appetite) gives the same answer without a key, for websites. Both are rate-limited.