Plan Approvals

Create pending approval rows for each post in a content plan — one row per post, status=pending. Use after submit_content_plan_for_approval to materialize the approval queue. Each entry in posts becomes a row that respond_plan_approval can later approve, reject, or edit. Idempotent on (plan_id, post_id) — calling twice with the same posts is a no-op for already-existing rows. Returns IDs of created items for use with list_plan_approvals.

List approval items for a content plan, optionally filtered by status (pending / approved / rejected / edited). Use to check what needs review before scheduling, or to audit decisions after the fact. plan_id comes from get_content_plan or save_content_plan. For a single items full state, get the plan via get_content_plan instead — that includes per-post approval data inline.

Approve, reject, or edit a single pending plan approval item. Use to act on items surfaced by list_plan_approvals. decision=edited REQUIRES edited_post containing the modified post fields — passing edited without edited_post returns an error. Once decided, an item cannot be re-decided (immutable transition). reason is optional but recommended for rejected or edited to leave a paper trail. After all items are decided, schedule_content_plan publishes only the approved (and edited) ones.