Unschedule an entry
Take an entry off the Calendar without sending it. The draft stays in the library, and an approved entry is no longer approved.
apiKeyAuthorizationBearer <token>API key for authenticating protected endpoints. Pass as Bearer token in Authorization header.
entryId*stringUnique identifier of the schedule entry
Body
application/json- body
Unscheduled
application/json- response
id*stringUnique identifier of the schedule entry
contentId*|The piece it sends: a content id, or a post id for an article
kind*stringWhat kind of piece goes out
"post""tweet""linkedin""x_article""newsletter"channel*stringWhere it goes, such as x, linkedin, or newsletter
status*stringplanned has a proposed time, scheduled is approved and waiting for its time, failed can be retried
"unplanned""planned""scheduled""publishing""published""failed""canceled"needsApproval*booleanTrue when it has a time and is waiting for approval
publishAt*|When it goes out, ISO 8601
publishedAt*|When it went out, ISO 8601
failureReason*|Why the last send failed
holdReason*|Why it's on hold, or null. A held entry isn't approved with the rest until you name it
accountId*|The X or LinkedIn account it posts from, from GET /v1/schedule/accounts
accountLabel*|That account's name, such as @paragraph
entryRevision*integerSend it back when changing the entry to refuse the change if it moved since you read it
curl -X POST "https://example.com/v1/schedule/string/unschedule" \ -H "Content-Type: application/json" \ -d '{}'{ "id": "string", "contentId": "string", "kind": "post", "channel": "string", "status": "unplanned", "needsApproval": true, "publishAt": "string", "publishedAt": "string", "failureReason": "string", "holdReason": "string", "accountId": "string", "accountLabel": "string", "entryRevision": 0}