approvals_rule
The organization's enabled approval rule, or null when none: whether posts need human sign-off before they may arm, who the approvers are, and how many must agree.
The organization’s enabled approval rule, or null when none: whether posts need human sign-off before they may arm, who the approvers are, and how many must agree. Read this to know whether to call approvals_request before scheduling or publishing — when a rule is on, arming an unapproved post refuses.
Input
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | no | Organization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization. |
Result
JSON on success. A refusal comes back as an error prefixed with its code (NOT_FOUND, FORBIDDEN, TOO_MANY_REQUESTS, …) and a message written to be acted on — read it before retrying.
The same operation elsewhere
This tool and the REST operation approvalsRule and the CLI command inklate approvals rule run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.