> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Idempotency

> Safely retry OrgX write requests.

Use idempotency keys when retrying write requests on endpoints that document
server-side idempotency support. This prevents duplicate writes when a network
failure leaves the original request outcome unknown.

## Header

```text theme={"dark"}
Idempotency-Key: 8b6e0c46-6e1e-4a64-a949-9cf4f4cb49e5
```

Keys should be:

* unique per logical operation
* stable across retries of the same operation
* generated by the client, not reused globally
* stored long enough for your retry window

## Preview Status

Idempotency behavior is being standardized across Public Preview write
endpoints. Until an endpoint marks `Idempotency-Key` as supported, treat the
header as a client-side correlation key and future-compatibility convention,
not a server-side dedupe guarantee.

## Retry Rules

| Situation                                 | Use same key?             |
| ----------------------------------------- | ------------------------- |
| Request timed out before response         | Yes                       |
| Received `500`, `502`, or `504`           | Yes                       |
| Received `429` and retrying after backoff | Yes                       |
| Validation failed with `400`              | No, fix the request first |
| User changed the operation                | No, create a new key      |