HEhedgespecialty
Submissions

Reply to Hedge on a submission (answer, revise, authorize a bind)

Changed on

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.

post/broker/submissions/{submission_id}/thread

Request

  • Base URL
    https://api.hedgespecialty.com/api/v1
  • Auth
    OAuth 2
    Authorization code: https://api.hedgespecialty.com/api/v1/oauth/authorize
    Client credentials
    Token URL: https://api.hedgespecialty.com/api/v1/oauth/token

Path parameters

submission_idstring uuid required

Headers

Idempotency-Keystring

Client-generated key; a retry with the same key replays or attaches to the original turn.

Request body

bodystring required

Your reply to Hedge, plain text. Written exactly as you would reply to Hedge's email.

document_idsstring[]

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).

producer_emailstring

REQUIRED when authenticating with a machine credential; the active portal user this reply is attributed to.

Response

Received; Hedge is answering asynchronously.

message_idstring uuid required

The thread id of your message (readable via GET .../thread).

status'received' required
detailstring required

Changes