Skip to main content

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​

NameValueDescription
AuthorizationApikey your-api-key-hereYour API key for authentication
Content-Typeapplication/jsonRequest body format

Body Parameters (JSON)​

NameTypeRequiredDescription
request_idStringYes*The request_id returned by the original async upload.
job_idStringYes*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_id nor job_id provided.
  • 404 Not Found — no upload found for the given identifier.
  • 409 Conflict — nothing to retry (no failed platforms).
  • 500 Internal Server Error

Retry reuses the media snapshot stored from the original upload. There is no need to send the file again.