Retry & Unpublish
Post-publish actions on an upload: retry a failed upload without re-uploading media, or unpublish (delete) a post that was already published to a platform.
Retry a Failed Upload
Re-enqueue an upload that failed on one or more platforms. Only the platforms that failed are retried; platforms that already succeeded are left untouched. The original media snapshot is reused, so you do not need to re-upload the file.
Endpoint
POST /api/uploadposts/posts/retry
Headers
| Name | Value | Description |
|---|---|---|
| Authorization | Apikey your-api-key-here | Your API key for authentication |
| Content-Type | application/json | Request body format |
Body Parameters (JSON)
| Name | Type | Required | Description |
|---|---|---|---|
request_id | String | Yes* | The request_id returned by the original async upload. |
job_id | String | Yes* | The scheduled job ID. Alternative to request_id. |
* Provide either request_id or job_id (one is required).
Example Request
curl -X POST https://api.upload-post.com/api/uploadposts/posts/retry \
-H 'Authorization: Apikey your-api-key-here' \
-H 'Content-Type: application/json' \
-d '{
"request_id": "3f7c2b1a-9d4e-4a2b-8c1f-1234567890ab"
}'
Successful Response (200 OK)
{
"success": true,
"request_id": "3f7c2b1a-9d4e-4a2b-8c1f-1234567890ab",
"message": "Failed platforms re-enqueued for retry"
}
Poll the upload status endpoint with the request_id to track the retried platforms.
Error Responses
- 400 Bad Request — neither
request_idnorjob_idprovided. - 404 Not Found — no upload found for the given identifier.
- 409 Conflict — nothing to retry (no failed platforms).
- 500 Internal Server Error
No re-upload required: Retry reuses the media snapshot stored from the original upload. There is no need to send the file again.
Unpublish (Delete) a Published Post
Delete a post that was already published to a platform. This removes the live post from the target network.
Platform support
| Platform | Deletion |
|---|---|
| ✅ | |
| YouTube | ✅ |
| X | ✅ |
| ✅ | |
| Threads | ✅ |
| ❌ | |
| TikTok | ❌ |
Instagram and TikTok do not support deletion via API. These platforms have no public endpoint to delete a published post, so the API returns a clear error if you attempt it.
Endpoint
POST /api/uploadposts/posts/unpublish
Headers
| Name | Value | Description |
|---|---|---|
| Authorization | Apikey your-api-key-here | Your API key for authentication |
| Content-Type | application/json | Request body format |
Body Parameters (JSON)
| Name | Type | Required | Description |
|---|---|---|---|
platform | String | Yes | One of facebook, youtube, x, linkedin, threads. |
user | String | Yes | Profile username (as configured in Upload-Post). |
post_id | String | Yes | The published post's ID on the target platform. |
Example Request
curl -X POST https://api.upload-post.com/api/uploadposts/posts/unpublish \
-H 'Authorization: Apikey your-api-key-here' \
-H 'Content-Type: application/json' \
-d '{
"platform": "youtube",
"user": "my-profile",
"post_id": "dQw4w9WgXcQ"
}'
Successful Response (200 OK)
{
"success": true,
"message": "Post deleted successfully"
}
Error Responses
- 400 Bad Request — missing fields, or an unsupported platform (e.g.
instagram,tiktok). - 403 Forbidden — the connected account is not authorized to delete the post.
- 404 Not Found — no post found for the given
post_id. - 500 Internal Server Error