Answer outstanding items in a batch
POST
/broker/submissions/{submission_id}/outstanding-requirements/answers
const url = 'https://api.hedgespecialty.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/outstanding-requirements/answers';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"answers":[{"key":"example","value":"example"}],"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/outstanding-requirements/answers \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "answers": [ { "key": "example", "value": "example" } ], "producer_email": "example" }'Apply typed answers to items the CURRENT outstanding view asks for
(keys not in that view are reported as skipped, never written).
Answers land on the submission brief and are routed to live
carrier sessions automatically. Requires the broker_submit
scope. Machine credentials must name producer_email.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”submission_id
required
string format: uuid
Request Bodyrequired
Section titled “Request Bodyrequired”Media typeapplication/json
object
answers
required
Array<object>
object
key
required
An item key from GET …/outstanding-requirements
string
value
required
Typed per the item’s input (string
producer_email
REQUIRED when authenticating with a machine credential; the active portal user the answers are attributed to.
string
Examplegenerated
{ "answers": [ { "key": "example", "value": "example" } ], "producer_email": "example"}Responses
Section titled “Responses”Truthful applied/skipped report
Media typeapplication/json
object
applied
Array<string>
skipped
Array<object>
object
key
string
reason
string
routed
Carrier sessions the answers were routed to
integer
Examplegenerated
{ "applied": [ "example" ], "skipped": [ { "key": "example", "reason": "example" } ], "routed": 1}Token lacks the broker_submit scope
Not found (or not your brokerage’s)
Missing/unknown producer_email for a machine credential