Send an Idempotency-Key header on any write. The same key with the same request returns the first answer for 24 hours, so a retry after a timeout cannot create a second post. The same key with a different request is a 409 conflict. Keys use letters, digits and . _ : - up to 100 characters.
Make a key per intended action, such as a campaign id plus the network.
Send it with the first request and with every retry of that request.
Treat a 409 as a bug in your code: the key was reused for something else.
Idempotency is separate from the rule that an unknown outcome is never retried by 1Post itself; see failures and unknown outcomes.
7-day trial for $1. Connect your accounts and schedule a week of posts in one sitting.
Start a trialCount characters the way each network does, split threads and preview posts. No account needed.
Open the toolsPost to every network from your own code or assistant with one key, signed webhooks and idempotent requests.
See the APIYes, send the same key. If the first request did create the post, you get that answer back instead of a duplicate.
Connect your accounts, write once and let 1Post publish on time while you get on with the rest of your day.