Reply to Hedge on a submission (answer, revise, authorize a bind)
const url = 'https://api.hedgespecialty.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/thread';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"body":"example","document_ids":["2489E9AD-2EE2-8E00-8EC9-32D5F69181C0"],"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/thread \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "body": "example", "document_ids": [ "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" ], "producer_email": "example" }'Identical in effect to replying to Hedge’s email. Use it to answer
a question Hedge asked, send a revision, attach documents you
already uploaded, or give a bind authorization (“bind the Kinsale
quote, effective 10/1”). Your message is recorded on the thread
and Hedge’s quarterback answers on the same submission; the answer
arrives in the thread and on the submission.message webhook,
typically within a couple of minutes. Requires the broker_submit
scope. Machine credentials must name producer_email.
Send an Idempotency-Key header (up to 128 characters, unique per
message) so a retried request attaches to the same turn instead of
sending your message twice.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Header Parameters
Section titled “Header Parameters”Client-generated key; a retry with the same key replays or attaches to the original turn.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Your reply to Hedge, plain text. Written exactly as you would reply to Hedge’s email.
Ids of documents you already uploaded to this submission (POST .../documents) to attach to the reply. Every id must belong to this submission (400 otherwise).
REQUIRED when authenticating with a machine credential; the active portal user this reply is attributed to.
Examplegenerated
{ "body": "example", "document_ids": [ "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" ], "producer_email": "example"}Responses
Section titled “Responses”Received; Hedge is answering asynchronously.
object
The thread id of your message (readable via GET .../thread).
Example
{ "status": "received"}A document id does not belong to this submission
Token lacks the broker_submit scope
Not found (or not your brokerage’s)
Blank body