Submit the bind request to Hedge for placement
const url = 'https://api.hedgespecialty.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/bind-requests/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/submit';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"attest_assumptions":false,"producer_email":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.hedgespecialty.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/bind-requests/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/submit \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "attest_assumptions": false, "producer_email": "example" }'The wizard’s own submit, same validation: the request moves from
drafted to submitted and Hedge places the bind with the carrier
(your brokerage’s approval settings decide whether a Hedge reviewer
looks first). While assumptions remain unconfirmed this answers 409
assumptions_unconfirmed, pass attest_assumptions in the body to
confirm and submit in one call. Surplus-lines placements need a
diligent search on file (422 says so); direct-bill card-payment lanes
are portal-only (422). A bound event follows on the events feed
and webhooks once the carrier binds.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Request Body
Section titled “Request Body”object
REQUIRED with a machine credential.
Responses
Section titled “Responses”The submitted bind request
object
drafted: checklist open (upload documents, confirm assumptions,
then submit). submitted/sent: Hedge is placing the bind with
the carrier. binder_received/bound: the placement completed
(the policy appears under GET /broker/policies and a bound
event is emitted). bind_failed: Hedge is reviewing.
The producing broker the request is attributed to.
Standing assumptions the retail agent still has to confirm. Non-empty means create/submit will answer 409 assumptions_unconfirmed until attested.
One assumption Hedge made to obtain the quote (a value it defaulted
on the carrier application because the file did not state it) that
the retail agent has not yet confirmed. key is what
attest_assumptions lists; label is the plain-language statement;
value is the exact value asserted to the carrier (absent when the
entry records none).
object
The asserted value
One pre-bind item the carrier needs, with your response state.
object
The carrier’s wording of the item.
While the request is drafted, the path to POST a PDF for this item (multipart file); null afterwards.
Envelope state of a signature request started for this item through the Hedge portal wizard (e.g. sent, completed, queued_for_review); null when none.
Plain-language actions for the current state, in order.
Example
{ "status": "drafted", "contingencies": [ { "kind": "question", "status": "pending" } ]}Broker_submit scope required
Submission or bind request not found
Assumptions unconfirmed, already submitted, or the selected quote changed
object
409 body from create/submit. The bind request exists as a draft
(bind_request_id); re-POST the create (idempotent for the same
quote) or POST submit with attest_assumptions to confirm.
object
One assumption Hedge made to obtain the quote (a value it defaulted
on the carrier application because the file did not state it) that
the retail agent has not yet confirmed. key is what
attest_assumptions lists; label is the plain-language statement;
value is the exact value asserted to the carrier (absent when the
entry records none).
object
The asserted value
Example
{ "detail": { "code": "assumptions_unconfirmed" }}Not yet submittable (effective date out of range