Retry Post API
The Retry Post API re-publishes only the failed platform targets of an existing post, either immediately or at a scheduled time. Use it when a multi-platform publish partially failed and you need to recover the unsuccessful destinations without rebuilding the original request. The retry reuses the original post content, media, and per-platform settings, and already-published platforms are skipped so they are not posted again.
Retry Post API overview and endpoint contract
When a post publishes to several platforms and one of them fails, you do not have to rebuild the whole request. The Retry Post API re-sends only the failed platform targets, drawing on the saved text, images or video, and destination-specific options from the first attempt. Destinations that already succeeded stay untouched: already-published platforms are skipped, so you never double-post. This makes the operation suitable for partial failures where some destinations succeeded and others did not.
The endpoint is shown in the endpoint example titled Retry Post API endpoint. The method and path must be used exactly as shown, with the origin supplied through the base URL placeholder. The postId path parameter identifies which existing post to retry, as detailed in the path parameters table.
Both body fields are optional. Omit the body to retry immediately. To schedule the retry, provide scheduledFor as an ISO 8601 time and, when needed, timezone as an IANA timezone such as America/New_York. The timezone defaults to UTC. The body parameters table lists the exact field names, types, and defaults.
Only destinations whose status is failed get another attempt. The retry reuses the original post's content, media, and per-platform settings, so you do not resend the payload. Credits are charged for the retried platforms, because they were refunded when they failed, and are refunded again if the retry fails too. Check the response contract after the call to confirm whether the retry is publishing now or scheduled.
Choose retry now when the failed destinations should be attempted immediately and there is no timing reason to wait. The worked example titled Retry now with cURL shows the immediate form with no request body. Choose schedule the retry when the attempt should happen at a specific future time, for example to align with a later publishing window or to avoid retrying during a known outage. The worked example titled Schedule the retry with cURL shows scheduledFor and timezone together. Before scheduling, verify that scheduledFor is in the future; otherwise the request returns a 400 response.
The response matches the Create Post response shape. The status field is pending or publishing for an immediate retry, or scheduled when you pass scheduledFor. The response also returns success, postId, scheduledFor, and a platforms array describing the retried platforms. The example titled Scheduled retry response example shows a scheduled response for a LinkedIn target. Treat a 202 response as acceptance of the retry, not as proof that every retried platform has finished publishing.
Use the status codes table as a failure checklist. A 400 response means No failed platforms to retry, or that scheduledFor is not in the future, so inspect the post's platform statuses and the scheduled time before calling again. A 402 response means Not enough credits to retry the failed platforms, so resolve the credit balance before repeating the request. A 404 response means the post was not found, so verify the postId. Do not retry blindly after a 400 or 404, because neither condition is fixed by sending the same request again.
| Parameter | Type | Required | Description |
|---|---|---|---|
| postId | string | Yes | The ID of the post to retry |
Exact source contract; origin modularized as {{API_BASE_URL}}.
| Parameter | Type | Required | Description |
|---|---|---|---|
| scheduledFor | string | No | ISO 8601 time to schedule the retry. Omit to retry right away. |
| timezone | string | No | IANA timezone for the scheduled retry (e.g. America/New_York). Defaults UTC. |
Both fields are optional. Omit the body to retry immediately.
| Code | Meaning |
|---|---|
| 202 | Retry accepted (publishing now or scheduled) |
| 400 | No failed platforms to retry, or scheduledFor is not in the future |
| 402 | Not enough credits to retry the failed platforms |
| 404 | Post not found |
Exact source status meanings.
Frequently asked questions
How do I choose between retry now and schedule the retry?
Omit the body to retry immediately. To schedule it, provide scheduledFor as an ISO 8601 time and optionally timezone as an IANA timezone, which defaults to UTC.
Will a retry post again to platforms that already succeeded?
Only destinations marked failed are sent again. Successful destinations are left alone, so already-published platforms are skipped and are not posted a second time.
What do the 400, 402, and 404 responses mean for a retry?
A 400 can mean No failed platforms to retry or that scheduledFor is not in the future. A 402 means Not enough credits to retry the failed platforms. A 404 means the post was not found.
POST {{API_BASE_URL}}/v1/posts/{postId}/retrycurl -X POST "{{API_BASE_URL}}/v1/posts/post_abc123/retry" \
-H "x-access-key: YOUR_API_KEY"curl -X POST "{{API_BASE_URL}}/v1/posts/post_abc123/retry" \
-H "x-access-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"scheduledFor": "2026-01-01T15:00:00Z",
"timezone": "America/New_York"
}'{
"success": true,
"status": "scheduled",
"postId": "post_abc123",
"scheduledFor": "2026-01-01T15:00:00.000Z",
"platforms": [{ "platform": "linkedin", "success": true }]
}