Cancel a draft or scheduled post
Cancels a post that has not gone out. A scheduled post is deleted in Zernio; a draft never reached Zernio at all and is simply marked `cancelled`. A post that already published answers the same 404 as one that does not exist, because Zernio refuses to delete a published post and putty does not expose unpublishing.
Cancels a post that has not gone out. A scheduled post is deleted in Zernio; a draft never reached Zernio at all and is simply marked cancelled. A post that already published answers the same 404 as one that does not exist, because Zernio refuses to delete a published post and putty does not expose unpublishing.
Authorization
bearerAuth A bearer token. The Account routes accept a Privy access token; the MCP transport accepts an sk- API key issued by POST /account/api-keys.
In: header
Path Parameters
The publish request id.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/social/posts/string/cancel"{ "id": "string", "projectId": "string", "platforms": [ { "accountId": "string", "platform": "string", "text": "string" } ], "assetIds": [ "string" ], "scheduledFor": "string", "status": "draft", "zernioPostId": "string", "lastError": "string", "approveUrl": "string", "createdAt": "string", "updatedAt": "string"}Approve a draft and publish it POST
**The only route that calls Zernio's create-post.** A user clicking Approve in the dashboard lands here; a model or an external MCP caller never does, which is why the tool hands back an `approveUrl` instead. Sends `scheduledFor` when the draft has one and `publishNow` when it does not, and moves the row out of `draft` before the call so a crash mid-publish cannot leave something a retry would post twice. Requires the caller's own Privy session: an `sk-` key cannot publish on a user's behalf, exactly as it cannot sign a transaction.
Post analytics for a connected account GET
Reads Zernio's post metrics for one connected account over a window, through the caller's own key. The account must be on the caller's Zernio profile; an account id belonging to someone else answers the same 404 as one that does not exist. Zernio's own maximum range is 366 days.