Skip to content

Correct the business's name, mailing address, contact, class or effective date

PATCH
/broker/submissions/{submission_id}/business
curl --request PATCH \
--url https://api.hedgespecialty.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/business \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "insured_name": "example", "mailing_address": {}, "contact": {}, "effective_date": "2026-04-15", "classification": {}, "expected_brief_version": 1, "producer_email": "example" }'

The portal’s business edit, open to connected apps and machine credentials (producer_email required for a machine credential). Any subset; omitted fields stay. The record is corrected, every market’s copy of the old value follows, and the markets re-prepare. A quoted market reads as a previous quote until you request it again.

submission_id
required
string format: uuid
Media typeapplication/json
object
insured_name
string
<= 300 characters
mailing_address

line1, line2, city, state, zip.

object
contact

name, email, phone.

object
effective_date

Today or within the next year.

string format: date
classification

naics (six digits) and optionally description (what the business does).

object
expected_brief_version

The version you read; a newer one returns 409.

integer
producer_email
string
Examplegenerated
{
"insured_name": "example",
"mailing_address": {},
"contact": {},
"effective_date": "2026-04-15",
"classification": {},
"expected_brief_version": 1,
"producer_email": "example"
}

The business as it now stands, what changed and which markets followed

business_edit_unavailable, or brief_changed: read the file again and retry

Invalid value (the message says what)