Send a risk
POST /broker/intake takes an email-style description plus ACORDs, loss
runs and supplements; POST /broker/submissions takes structured JSON.
Either one creates the submission and starts the run. Pass hold: true
to defer it.
Hedge Broker API
The Hedge broker API works the way emailing Hedge a risk works: one call in, the system runs. Send the risk as free text and PDFs (or structured JSON), and Hedge extracts it, matches carrier appetite, emails the producer the clearance listing every market being tried, opens the market lanes, and quotes the instant-quote markets. Then read the markets back in three categories, follow the conversation, answer what only your brokerage can answer, and bind, all from your own software.
What you can do
Section titled “What you can do”Read the markets
GET /broker/submissions/{id}/markets returns every lane in three
categories, Hedge Instant Quote, Hedge Binding and Hedge Specialty, with
what each still needs from you, the assumptions Hedge made on your behalf,
and released quotes.
Talk to Hedge
GET .../thread mirrors the emails Hedge sends the producer; POST .../thread replies exactly as an email reply would. Webhooks push new lane
events and messages to your endpoint.
Bind
POST .../bind-requests is the broker’s bind authority over the API. The
assumptions behind an instant quote must be attested explicitly; the API
answers 409 assumptions_unconfirmed with the list until they are.
Build your own application
GET /broker/programs/{id}/application-schema is exactly the question set
an instant-quote carrier asks. Collect answers in your own UI and save them
through the application workspace.
Read the book
Submissions, policies, policy documents, payments and appetite, all scoped to your brokerage.
Three ways to integrate
Section titled “Three ways to integrate”They share one API, one OAuth 2.1 model, and one set of scopes.
hedge CLIFor people and scripts. hedge intake sends a risk, hedge markets reads the three categories, hedge thread and hedge reply carry the conversation, hedge bind binds.
REST APIJSON (and multipart for files) over HTTPS with bearer tokens. The same endpoints the portal and CLI use, from your backend.
MCP connectorFor AI tools like Claude, ChatGPT, Cursor and Codex. Reads your book and the market categories; with write access it creates submissions and requests binds with your attestation.
Access
Section titled “Access”Every brokerage on Hedge has API access. Machine credentials (API keys) are
created self-serve in the broker portal under Settings → API keys and
exchanged for short-lived bearer tokens with the client_credentials grant.
The CLI and the MCP connector use the same OAuth 2.1 server with per-user
sign-in. See Authentication.
Base URL
Section titled “Base URL”All REST endpoints live under a single versioned base URL:
https://api.hedgespecialty.com/api/v1Every request carries a short-lived OAuth 2.1 bearer token, and all data is scoped to the brokerage the token belongs to. Changes are additive on this version; breaking changes ship as a new version with notice.
Next steps
Section titled “Next steps”QuickstartSend a PDF, read the markets, read and answer the thread, register a webhook, bind.
AuthenticationDevice flow, browser sign-in, dynamic client registration, client credentials, and scopes.
ConventionsThe three categories, producer_email for machine credentials, 409 assumptions_unconfirmed, cursors, idempotency, webhooks event_types.
API ReferenceEvery endpoint, request, and response, generated from the OpenAPI spec.