Idempotency
How to avoid duplicate social posts with Postifys today without a public Idempotency-Key header - using history, queues, and safe retries.
Quick answer: Postifys does not yet document a public
Idempotency-Key header. Prevent duplicates by checking queue/history state before resubmitting the same media job.Current safe practice
- Submit one publish request per intended destination post.
- If the client times out, query Post History / status for the same account+media before sending again.
- Do not parallel-spam the same Reel/video while a lane job is still queued or processing.
- Use dashboard retry for failed Facebook/Instagram jobs when available instead of inventing a second payload.
Why duplicates happen
- Client retries on network timeout while the original job is already queued on a platform lane.
- n8n workflow re-runs without checking prior node output/history id.
- Multiple workers sharing one API key without coordination.
Roadmap honesty: A first-class idempotency-key API may be added later. Until then, treat history IDs and queue state as your dedupe mechanism.