Skip to Content
GrowSocialelion API
posts:approve endpoints

Approve a post, a series or a series part

APPROVE, for any workspace whose key holds 'posts:approve'.

POST /api/v1/approve · MCP tool approve · scope posts:approve

APPROVE, for any workspace whose key holds 'posts:approve'. kind 'post': one pending Inbox draft (id = proposalId), scheduled through the Inbox's own Schedule service at scheduled_at or its requested time. kind 'series': a whole PROPOSED series (id = seriesId), like the app's Approve button; refused when its estimate does not fit the credits or the brand's monthly cap. kind 'series_part': one video part of a SCHEDULED series (id = seriesId, part = number or episode id) whose video is rendered: its Inbox card per network is made if needed and approved onto the series time. Server caps on every call: the key's networks, the agent's halt switch and the brand budget, each channel's Posts-per-day cap on that day, and at most 50 approvals per key and 100 per workspace per UTC day. Nothing is sent now; every publish check still runs at send time. Idempotent: an already approved item comes back as it is.

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

NameTypeRequiredDescription
kind"post" | "series" | "series_part"YesWhat to approve.
idstringYespost: the proposalId. series / series_part: the seriesId.
partinteger | stringNoThe part: its number (1, 2, ...) or its episode id (from get_series).
scheduled_atstringNokind 'post' only. An absolute future time with an offset, e.g. 2026-11-23T09:00:00Z.

Request

curl -X POST https://growsocialelion.com/api/v1/approve \
  -H "Authorization: Bearer gse_mcp_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"post","id":"prop_123","scheduled_at":"2026-11-23T09: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",
  "code": "string",
  "state": "string"
}

Errors use the shared body. See Errors. The full schema is in the API reference.