Change an entry's account
Post an X or LinkedIn entry from another connected account. The entry is held until it's approved again.
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
accountId*stringFrom GET /v1/schedule/accounts
1 <= lengthentryRevision?integerFrom the entry you reviewed, to refuse a stale change
Account changed
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/account" \ -H "Content-Type: application/json" \ -d '{ "accountId": "string" }'{ "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}Hold an entry POST
Pause an entry where it is on the Calendar. It won't go out, and approving everything skips it, until you approve it by name.
List content groups GET
Retrieve the content groups in your publication, most recently active first. The publication is identified by the API key. A group ("bucket") is one identity for a post and everything made out of it — the post, the X thread drawn from it, the LinkedIn version, the newsletter. It's what the writer sees as a single stacked row under Content. Each group lists its members in display order, with the post it was seeded from first. Bodies aren't included; fetch the member with `GET /v1/content/{id}` or `GET /v1/posts/{id}` to read one.