Broker Finalize Submission

POST

/api/v1/broker/submissions/{submission_id}/finalize

curl --request POST \
  --url https://example.com/api/v1/broker/submissions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/finalize

Run the same carrier-match + propose-send chain the inbound-queue “Create New Submission” runs. The wizard’s upload path calls this after forms are uploaded + extracted, so the brief is populated first. Per- brokerage auto-approve still gates whether the resulting carrier-email PendingActions auto-dispatch or wait in the approvals queue. (The assistant path doesn’t call this, its session-close ingest already matches carriers.) If the enqueued task is dropped or crashes, the never-marketed sweeper (submissions.sweep_pending_intake_qb_ingests) re-fires it off the submission_source='broker_portal' stamp + broker-uploaded docs.

Parameters

Path Parameters

submission_id

required

Submission Id

string format: uuid

Responses

202

Successful Response

Media typeapplication/json

Response Broker Finalize Submission Api V1 Broker Submissions Submission Id Finalize Post

object

key

additional properties

string

Example^generated

{
  "additionalProperty": "example"
}

422

Validation Error

Media typeapplication/json

HTTPValidationError

object

detail

Detail

Array<object>

ValidationError

object

loc

required

Location

Array

msg

required

Message

string

type

required

Error Type

string

Example^generated

{
  "detail": [
    {
      "loc": [
        "example"
      ],
      "msg": "example",
      "type": "example"
    }
  ]
}