Skip to content

The flow

Appetite→Requirements→Create→Answer→Follow→Quotes→Bind
  1. Appetite. POST /appetite. Anything but a good fit includes how_to_send: the submissions address and what to include. A broker reviews everything, including files outside appetite.

  2. Requirements. POST /requirements lists what the class needs, each with a key and an answer type, so you collect it up front.

  3. Create. POST /submissions with the facts you have, or POST /intake with documents and a description. Always send client_reference: a retry returns the same file.

  4. Close the gaps. PATCH /submissions/{id}/answers and document uploads. One answer fills every market that asks it.

  5. Follow. Webhooks or GET /events, plus GET /submissions/{id} for status, what’s needed, anonymous market progress and your broker.

  6. Quotes. GET …/quotes once your broker presents them, with the quote documents in GET …/documents.

  7. Bind. POST …/quotes/{quote_id}/bind-request with your written instruction. Your broker confirms with the market and sends the binder.