Broker Submission Requirements
const url = 'https://example.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/requirements';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/requirementsThe live “what does this submission still need” view: per-market readiness (deterministic, no LLM on this read), carrier-API question gaps, the resolved application-form set, and documents already on file.
Accepts a portal session OR a connected app’s broker_submit OAuth token (Bindly / broker agents poll this between answering and finalizing).
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”Successful Response
The one ‘what does this submission still need’ composition: per-market readiness (deterministic, no LLM in this read), live carrier-API question gaps, the resolved application-form set, and the documents already on file. Broker-safe labels only.
object
One matched market’s readiness. needs_from_you are the gap labels
only the broker can supply; hedge_obtains are items Hedge fetches
itself (loss runs, enrichment), informational, no action needed.
object
One live carrier-API quote session and its current gaps. Answer the
missing_questions via the api-quotes answers endpoint (or the
save_carrier_answers MCP tool), then close the session to quote.
object
object
Example
{ "form_fill_active": false, "carrier_api_sessions": [ { "completion_pct": 0, "has_quote": false } ]}Validation Error
object
object
Examplegenerated
{ "detail": [ { "loc": [ "example" ], "msg": "example", "type": "example" } ]}