Skip to main content

Outcome

You inspected every readiness issue, patched only contract-valid rejected Company fields, and re-read the exact company before any later Case finalization. Readiness remediation never changes Partner authorization. Incomplete companies remain readable and editable and may create Case drafts. Finalization re-evaluates readiness atomically. Evaluate case_access separately; green readiness does not prove consent or access.

1. Read the full current report

Render the entire case_submission_readiness.issues array. Every field starts with company. (for example company.payout_bank_account.account_holder); strip that prefix and map the first remaining segment plus code to owned input. Never stop at the first item or infer requirements from nullable response fields. A company.legal_representatives issue with code representative_required names the missing role as an English code, for example A legal representative with type "supervisory_board" is required. Resolve it by sending the complete legal_representatives array with a representative of that type; the array replaces the stored one.

2. Prove the sandbox before PATCH

3. Patch only the rejected root field

An owned array replaces the entire array. Omit notification_channels and legal_representatives unless full replacement is intended. Re-sending an object or array equal to the stored one — address, legal_representatives, notification_channels, payout_bank_account, or an unchanged data_sharing_basis — is a no-op: stored ids stay, and updated_at and the ETag do not move. Company PATCH never accepts users; correct memberships through their nested resources.

4. Re-read current readiness before finalization

Runnable readiness workflow

Python workflow

Representative response

Failure and recovery

  • 400 validation_error: branch on the returned field/code and send a new, minimal PATCH; never resend a stale full company.
  • A PATCH timeout is reconciled through the exact company URL before another correction. Company PATCH has no idempotency-key contract.
  • 409 company_identity_locked requires the authorized non-API correction process for a real locked-field change.
  • Access unavailable is not a readiness-remediation endpoint. Stop delegated traffic and handle access separately.