Final submission approval

Use this guide when an authorization asks for approve_submission. This is the review step before an irreversible payer submit boundary.

When approval appears

approve_submission can appear when:

  • the authorization was created with policy.finalSubmission = requires_approval
  • Collate reached the final payer-submit boundary
  • sandbox or another safety gate prevents automatic final submit
  • Collate needs reviewer acknowledgement before a submit-capable manual handoff

Do not assume approval appears only for one policy value. Always follow the current authorization response.

Review snapshot

submission.reviewSnapshot is embedded on the authorization.

1{
2 "id": "rev_123",
3 "status": "current",
4 "kind": "final_payer_submission",
5 "generatedAt": "2026-05-22T18:15:00Z",
6 "covers": {
7 "priorAuthorizationVersion": 17,
8 "requirementsVersion": 4,
9 "answersVersion": 8,
10 "attachmentsVersion": 2
11 },
12 "summary": {},
13 "answers": { "item": [] },
14 "attachments": [],
15 "warnings": [],
16 "transparency": {
17 "liveSessionEndpoint": "/v1/prior-authorizations/auth_123/live-session"
18 }
19}

Route summary, answers, attachments, and warnings to the approval authority. That can be a reviewer, a policy service, or another controlled backend process. Treat warnings as approval-visible information, not validation errors.

Approve

1

Read the latest authorization

Read immediately before approval so the reviewer sees the current snapshot.

2

Present the current snapshot

Present the current submission.reviewSnapshot to the approval authority and record the snapshot ID it accepted.

3

Confirm with the accepted snapshot ID

1POST /v1/prior-authorizations/auth_123/confirm
2Authorization: Bearer <API_KEY>
3If-Match: "17"
4Content-Type: application/json
5
6{
7 "acceptedReviewSnapshotId": "rev_123"
8}

After approval, Collate owns processing again.

Stale snapshots

Answer or attachment writes can change the package. If you approve an old snapshot, the API returns 409 review_stale.

Recover by reading the latest authorization, presenting the new snapshot, and confirming with the new authorization version and snapshot ID.

Live review

Use Live sessions to show a read-only payer-channel view while the case is active. Live-session grants are transparency tools; the authorization remains the source of truth for whether final approval is open.