Developer docs / Publishing tasks
Cancel a publishing task
Cancel a publishing task that has not reached a terminal state by using its postId.
POST
/v1/creator/post/cancel- Authentication:
- Request header x-api-key: <YOUR_API_KEY>; keep the key on the server and never expose it in client code, logs or shared files.
- Success criteria:
- HTTP 2xx with code=0; for asynchronous tasks, also query the final status.
Request body fields
| Field | Type | Required | Description |
|---|---|---|---|
postId | string | Yes | postId returned when the publishing task was created |
A completed, failed, or already cancelled task cannot be cancelled again.
Request body
{
"postId": "post_xxx"
}Success response
{
"code": 0,
"data": null,
"message": "success"
}Response and errors
Main response fields come from the published contract; see the JSON Schema. Required refers to the constraint in the containing object.
| Field | Type | Required | Description |
|---|---|---|---|
code | integer | Yes | Fixed value: 0 |
data | null | Yes | — |
message | string | Yes | — |
timestamp | integer | No | Response timestamp in milliseconds. |
HTTP 400The request parameters or body are invalid. Fix them and retry.HTTP 401The API key is missing or invalid. Check x-api-key.HTTP 403The API key has no permission to call this endpoint.HTTP 429Too many requests. Retry with exponential backoff.HTTP 500The server failed. Retry transient failures with exponential backoff.
Fix parameter, permission or authorization errors before retrying. If task creation times out, query existing tasks first and do not submit duplicates after an interrupted poll.
Last updated · 2026-11-16