Approve and schedule a pending draft
APPROVE one pending Inbox draft and schedule it, exactly as the Inbox's Schedule button does: the same guards, an approval bound to the draft's exact te...
POST /api/v1/approve_post · MCP tool approve_post · scope posts:approve
APPROVE one pending Inbox draft and schedule it, exactly as the Inbox's Schedule button does: the same guards, an approval bound to the draft's exact text and media, and the row filed as scheduled. It is sent at scheduled_at by the normal scheduler, through every publish check; nothing is sent now. scheduled_at (ISO time with an offset) overrides the draft's requested time; without it the requested time is used. Only a pending draft of this brand. Idempotent: an already scheduled or published draft comes back as it is. Needs the key's 'posts:approve' scope, which only allowlisted workspaces can grant.
Scope. Approve a pending Inbox draft and schedule it, with the same checks as the Inbox's Schedule button. A separate scope: never on by default, and only allowlisted workspaces can grant it. This endpoint never costs credits.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
post_id | string | Yes | The draft's proposalId (from propose_post or list_posts). |
scheduled_at | string | No | Optional. An absolute future time with an offset, e.g. 2026-11-21T09:00:00Z. |
Request
curl -X POST https://growsocialelion.com/api/v1/approve_post \
-H "Authorization: Bearer gse_mcp_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"post_id":"prop_123","scheduled_at":"2026-11-21T09:00:00Z"}'Response
200 with the tool's answer. The shape below is generated from the output schema; real answers can carry more fields.
{
"status": "string",
"reason": "string",
"post_id": "string",
"state": "string",
"scheduled_at": "string",
"platform": "string"
}Errors use the shared body. See Errors. The full schema is in the API reference.