Approve scheduled posts

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Approves calendar posts, moving each one from proposal to scheduled.

Approving doesn't publish anything and doesn't reserve anything. It marks which posts you want sent, and Start scheduling posts is what hands them to the publisher.

Approval is a selection, so one unusable ID never discards the rest. The request succeeds even when no ID could be approved, and the response reports each one:

  • approved: the post is now scheduled.
  • not_found: the ID names no live post of this app.
  • rejected: past the point of approval, with the status that blocked it.

Repeated IDs are collapsed, and re-approving a post that's already scheduled reports it under approved without changing anything, so calling twice returns the same body.

Send between 1 and 50 IDs.

post/api/apps/{app_id}/social-calendar/posts/approve

Path parameters

app_idstring required

ID of the app whose social calendar you want.

ID of the app whose social calendar you want.

Request body

post_idsstring[] required

IDs of the posts to approve, 1 to 50 of them, as returned by List scheduled posts. Repeated ids are collapsed.

Example request

{
  "post_ids": [
    "6886b8d390dc7e2f4a2c91b3",
    "6886b8d390dc7e2f4a2c91b4"
  ]
}

Response

The outcome of each ID you sent.

approvedstring[]

IDs of the posts that are now scheduled, including any that already were.

not_foundstring[]

IDs that name no live post of this app, because the post never existed or was deleted.

Example response

{
  "approved": [
    "6886b8d390dc7e2f4a2c91b3"
  ],
  "not_found": [
    "6886b8d390dc7e2f4a2c91b9"
  ],
  "rejected": [
    {
      "id": "6886b8d390dc7e2f4a2c91b4",
      "status": "posted"
    }
  ]
}

Changes

No recorded changes to this endpoint across all 14 revisions of this API.