Errors
state_authorisation_required
409 — the operation requires an authorising Resolution that has not been recorded.
Last updated
Cause
A category of Matter operations — equity issuance, share-class changes, board appointments, authorized-shares increase, dissolution — are legally consequential and require an authorising governance Resolution before they can execute. state_authorisation_required fires when the operation references no authorizing_resolution_id, or the referenced Resolution does not authorise this specific action.
Matter's Resolution model is the canonical anchor for "the board said so" and "the stockholders said so". An operation that mutates the entity in a way that requires consent must point at the Resolution that grants that consent. This is the API-level equivalent of attaching the signed board-consent PDF to the certificate filing.
Fix
- Identify which Resolution authorises the action. The
detailon the problem response names the kind of resolution required (board, stockholder, special committee). - If the resolution already exists, pass its
res_*id asauthorizing_resolution_idon the retry. - If the resolution does not exist, create it via
createResolution. The Resolution model captures the resolved text, the consent signatures, and the effective date. - Some actions also require
state_esra_consent_required— re-read the operation's prerequisites in the API reference for the full set.
Related codes
state_esra_consent_required— an electronic signature consent is missing.state_transition_invalid— the resource cannot make this transition at all.scope_tier_insufficient— the token isn't authorised for the operation's tier.