Reference
Idempotency
Make create and send requests safe to retry with the Idempotency-Key header.
Updated Oct 14, 2026
Networks are slow and connections drop. To retry a request without publishing or sending twice, send an Idempotency-Key header with a unique value, such as a UUID or your own record ID:
curl -X POST https://api.socialit.com/v1/posts \
-H "Authorization: Bearer $SOCIALIT_API_KEY" \
-H "Idempotency-Key: 6f1c2a8e-launch-2026-10-14" \
-H "Content-Type: application/json" \
-d '{ "content": "Hello", "account_ids": ["sa_2Jx0Fq5Pz8vYkB3mN6rT1wQ9sLd"], "publish_now": true }'- Every
POSTthat creates, sends or runs an action accepts the header. Each endpoint in the API reference that honours it lists theIdempotency-Keyheader (and the OpenAPI document marks it withx-idempotent: true). - Keys are 1 to 255 characters of
A-Z a-z 0-9 _ - : .and are scoped to the workspace and the operation. - Socialit stores the first successful (
2xx) response for 24 hours. Repeating the request with the same key and body returns it again withIdempotent-Replayed: true, without doing the work twice. - The same key with a different body answers
422 idempotency_key_reused. A duplicate sent while the first is still running answers409. - Error responses are not stored: fix the request and retry with the same key.