Skip to content
ShapelessAI← Back
Publishing

Review the queue

Read everything proposed, scheduled and published on the account, then act on it: approve a proposal (proposed becomes scheduled), dismiss it, publish a queued post now, edit a still-scheduled post's time, text, media or target account, cancel it, or ask for a rework from feedback.

View as Markdown

A batch resolves in one call. Every draft the agent team makes lands here first, so this is where a human, or the agent acting for one, says yes.

Ask in plain words

  • "what is waiting for my approval"
  • "approve the two LinkedIn posts you would pick"
  • "move Thursday's post to Friday 6pm"
  • "publish the queued post now"
  • "cancel the scheduled TikTok"

From an agent host (MCP)

Server: https://shapelessai.com/mcp (add it to your host).

  • posts_list: The post queue: proposed drafts, scheduled posts, published history, newest first. For "my best posts": sort views ranks every published post by views (metrics.latest.impressions) across the whole history, narrowed by platform, connectionId, minViews and since. Each reading carries its fetchedAt; fresh re-reads the listed posts' numbers older than 6h from the platforms first (slower, up to ~30s). Needs the read scope.
  • posts_get: One post's live state, with the url that opens it in the calendar for the human. Needs the read scope.
  • posts_approve: PUBLISHES CONTENT: approving moves proposals to the schedule, and they will go out. Needs the publish scope.
  • posts_dismiss: Cancel posts: proposed, scheduled, failed or handed-off. Nothing already publishing or published is touched. Pass the user's reason when they gave one; it teaches the agent their taste. Needs the write scope.
  • posts_publish: PUBLISHES CONTENT NOW: pushes a queued post to the platform immediately. Needs the publish scope.

From code (REST)

Bearer API key with the scope each call names (auth, OpenAPI).

  • GET /api/posts (read scope): The queue: proposed, scheduled, published, newest slot first. ?status= and ?limit= narrow it; ?from=&to= (ISO instants, up to 400 days apart) is every non-canceled post in that span, oldest first, whatever the account holds.
  • GET /api/posts/{id} (read scope): One post's live state.
  • PATCH /api/posts/{id} (write scope): Edit a still-scheduled post: time, text, media, settings, first comment, or the target account (same platform).
  • DELETE /api/posts/{id} (write scope): Cancel a post. The window: while it is proposed, scheduled, failed or handed off, so until publishing starts at scheduledAt; ?reason= says why.
  • POST /api/posts/{id}/approve (publish scope): Approve one proposal: proposed -> scheduled.
  • POST /api/posts/{id}/publish (publish scope): Publish a scheduled or failed post now. status failed is still a 200; its error says what the platform refused.
  • POST /api/posts/{id}/mark-posted (publish scope): Record that you posted it yourself.
  • POST /api/posts/{id}/revise (write scope): Rework a draft from feedback.
  • POST /api/posts/resolve (publish scope): Resolve posts: {ids, verb: approve|dismiss}. Approve takes proposed posts; dismiss cancels proposed, scheduled, failed or handed-off ones. Dismiss costs write.

The body

PATCH /api/posts/{id}:

  • scheduledAt string
  • postText string
  • mediaKeys array
  • settings object
  • connectionId string: Another connected account on the same platform.
  • firstComment string | null: null clears it.

From a terminal (CLI)

  • shapeless posts list
  • shapeless posts show
  • shapeless posts approve
  • shapeless posts dismiss
  • shapeless posts publish
  • shapeless posts mark-posted

Example

curl -s "https://shapelessai.com/api/posts?status=proposed" -H "Authorization: Bearer $SHAPELESS_API_KEY"
// MCP tool call
{ "tool": "posts_approve", "arguments": { "ids": ["<postId>"] } }
shapeless posts approve <id>

Refusals

StatusMeaning
400A query parameter the route refuses (unknown status, limit out of range, minViews or since without sort=views, a bad from/to); the message names it.
404No such post.
400A malformed field (scheduledAt, postText, settings, firstComment, connectionId), a mediaKey outside this account, an unconnected account, or nothing to change. The message names it.
409Already publishing, or the new account is another platform.
422A platform rule refused the edit, a mediaKey names nothing storage holds, or a sound without a connected Instagram account. The message names it.
409Not cancellable: publishing has started, the post is already published or canceled, or no such post on this account.
402A plan limit (PlanLimit).
409Not proposed, or a gate names what to edit first ({error}). Or needs a connected account: {needsConnection, connect: {platform, url, expiresAt}} - hand connect.url to the human.
409Not scheduled or failed, no connected account, or already publishing.
422TikTok refuses the post's settings; the error names them.
409Only a proposed or handed-off post can be marked as posted.
400No feedback, or more than 2000 characters.
409Only a proposed or scheduled post can be reworked.
400No verb, no ids, or more than 100 ids.
409Approve stopped clean, nothing changed: {needsConnection, connect} or {error} naming the post a platform rule refuses.

Where else

More in Publishing

Publish a post · Attach a sound to an Instagram Reel · Set the posting schedule · Answer comments and work the inbox

Every capability · Docs · /llms.txt