Learn how to retry API requests without performing the same operation twice
POST
and PATCH
operations, ensuring the safety and reliability of your requests, particularly in scenarios where network issues or communication problems can introduce uncertainty into request outcomes. Idempotent requests are essential for business-critical applications, such as for ensuring only once delivery of your notifications.
Idempotency-Key: <key>
header in your request. The idempotency key should be a unique client-generated value with sufficient entropy to prevent collisions. We recommend using V4 UUIDs as your idempotency keys.
Idempotency-Replay: true
header is included in the response.
<key>
exceeds 255 characters, the API will respond with a 400 Bad Request
error.422 Unprocessable Entity
error.409 Conflict
error along with a Retry-After
header.