Overview
Some endpoints accept an Idempotency-Key header to prevent duplicate processing of sensitive requests.
These requests take an Idempotency-Key header:
- Generate the key on your API client.
- The key should have 1 to 128 characters.
- The allowed characters are:
[A-Za-z0-9_-].
Idempotency behavior
Passing a duplicate idempotency key with the original payload returns the original result without re-processing the original action. Some fields may have been updated since the original request, as we do not store the original result. Additionally, fields like createdAt or updatedAt may not match the original request time exactly due to latencies and differences in timestamp formats.
Passing a duplicate idempotency key with a changed payload throws HTTP 409 IDEMPOTENCY_CONFLICT and no action is taken.