Skip to main content
POST
Resume interrupted publishing
Write access: a member/administrator with a write-enabled credential, or an authorized signed-in user. Resume an interrupted account’s unpublished posts using its current version. Confirm the account and remaining content with the user. Published posts are preserved; uncertain results cannot be resumed. Reuse the same idempotencyKey for retries. Resume one connected account’s failed remainder without creating a new posting group. Confirmed posts, their IDs and original request key are preserved. Active, cancelled or uncertain sequences cannot be resumed. Reuse the same resume key and payload after a lost response. A new failure requires a new key and the latest group version. MCP clients can use resume_post for this operation. Request conventions · API keys · MCP connections

Authorizations

Authorization
string
header
required

Personal or team Posted REST API key

Path Parameters

postId
string<uuid>
required

The postId from the corresponding list, record or authorization response.

Body

application/json
connectionId
string<uuid>
required
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
version
integer
required
Required range: x <= 9007199254740991
idempotencyKey
string
required
Pattern: ^[A-Za-z0-9._:-]{8,128}$

Response

Successful response. Examples are illustrative; field values vary by record.

post
object