Retry the same action
Public POST requests accept an optionalIdempotency-Key header. If a response is lost, retry the same request with the same key to avoid repeating the operation.
Use a new random UUID for each intended action, enclosed in double quotes inside the header value:
400 invalid_request.
Reuse keys for retries
A key belongs to one workspace and API credential. For 24 hours, the same key and request replay the original status and body. Keep the HTTP method, path, query parameters and body unchanged. Use a different key for a separate intended action, even when its content is identical. After the 24-hour retention period expires, the same key can execute again.Handle retry errors
Replays check current resource permissions. A denied replay does not execute the operation again or erase the saved result. The error body’s request ID can belong to the original request; the
X-Request-Id header identifies the current attempt.
Content updates
PUT /v1/files/{id}/content is not covered by this header. Follow Updating content to inspect the live state and changes in review after an interrupted content update.