Submissions

Read the conversation with Hedge on a submission

Changed on

Everything Hedge has said to your brokerage about this submission and everything your brokerage said back, oldest first: the clearance email, questions, market-plan updates, quote deliveries, your email replies, and messages exchanged with the assistant (through the portal or POST .../thread). Each item is a ThreadMessage; body_text is always plain text. Carrier and insured correspondence is never included.

The end-of-stream signal is the cursor, never page length. A non-null next_cursor means more messages may exist: store it and poll again with since=next_cursor until you receive a null. next_cursor is null only when the request proved your position is the tail. Message ids are stable, so re-reading an older cursor is always safe (dedupe by id). Prefer the submission.message webhook for push delivery of the same objects.

get/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

Query parameters

sincestring

Opaque cursor from a previous page's next_cursor; returns messages strictly after it. Omit to read from the beginning.

limitinteger

Max messages per page. Values outside [1, 200] are clamped, never rejected.

Response

One page of messages plus the follow-up cursor

next_cursorstring nullable

Changes