Idempotency and retries
Retry interrupted requests without creating a second publishing job.
Keep one request ID per operation
TikTok video, Instagram instagram, YouTube youtube, and Facebook facebook inputs each contain a UUID requestId. Generate it once before sending a publish or schedule request, store it with the complete input, and reuse both when retrying that operation.
The same ID and unchanged input return the existing job. A changed account, content, ordered media, options, or schedule can produce 409 REQUEST_CONFLICT. Create a new ID only when you intend a new operation. Replays still check current access and applicable limits.
Threads, X, and LinkedIn text requests do not have this requestId-based guarantee. If a response is lost, check whether the post was published before resending. A new request may publish the text again.
Interpret a replay
| Operation | Active job | Published job | Failed, canceled, or unknown job |
|---|---|---|---|
| TikTok/Instagram/YouTube immediate publish | 202 | 200 | 502 |
| Facebook publish or schedule | 202 | 200 | 200 with success: false |
For new schedules, TikTok retains HTTP 200; Instagram, YouTube, and Facebook return HTTP 202. Save jobId and scheduledPostIds and use the status endpoint to interpret the existing job. An HTTP status alone does not prove publication.
Handle uncertain outcomes
If the HTTP connection drops, retry an asynchronous operation with the saved ID and identical input. If a job is already unknown, Posteady does not submit it again automatically. Inspect the target social account before deciding whether a new request is needed. A different request ID can duplicate a post that actually reached the platform.
For failed, inspect the job's error first. Replaying the old request returns that failed job; it does not restart it. Resolve the cause before creating an intentional new operation.
Handle partial text failures
Multi-account text publishing returns HTTP 200 when at least one account succeeded, and HTTP 502 when all targets failed. Inspect each result's success, postIds, and error. A thread can fail after some posts have already been published. Do not resend the entire multi-account request without checking those IDs.