Idempotency

Send an Idempotency-Key header (any unique value up to 255 characters, such as a UUID) on POST and PATCH requests so a retry after a network error cannot do the work twice. For 24 hours, repeating the request with the same key returns the first response (with Idempotent-Replayed: true) instead of running it again. Using the same key for a different request returns 422 with code idempotency_key_reused; retrying while the first request is still running returns 409 with code idempotency_in_progress and a Retry-After header. A key whose first request never finished (the connection dropped and the server stopped) can be used again after five minutes. Requests made with a signed-in session take the header too; their keys are kept apart from your API keys’ keys.