Read a submission's package
const url = 'https://api.hedgespecialty.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/package';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.hedgespecialty.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/package \ --header 'Authorization: Bearer <token>'What you send your own markets for one of your submissions: its risk summary and the application documents to go with it.
summary has status (none until one is written, then ready),
text, sections, generated_at and stale (true once the file’s
facts changed after it was written; a portal session regenerates it).
The text is written for an underwriter from the file’s own facts and
every answer given on it, and lists no documents: add the ones you
send. sections is the same summary as titled sections in display
order, each with items (label, null for a plain line, and a
formatted value) and in_copy: the sections where it is false
(answers that differ between applications, and what Hedge assumed to
get a quote) are for you and are never in the text.
groups lists the documents: forms (the current version of each
form Hedge prepared), prefilled (your ready “Get a form” copies) and
documents (what you uploaded or emailed). Each has id,
file_name, attachment_label, selected (ticked by default) and,
when it isn’t ticked, a note saying why: a fill Hedge’s checks
doubt, another market’s quote or binder, a blank copy or a broker of
record letter. Carrier quote PDFs, bind uploads and internal filing
paperwork are never listed.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”The package
Not found (or not your brokerage’s)