# idempotency_conflict — Shorty API error

> Idempotency conflict (HTTP 409): when the Shorty API returns the idempotency_conflict error, why, and how to fix it.

| Code | HTTP status | Type URI |
| --- | --- | --- |
| `idempotency_conflict` | 409 | `https://aishorty.com/docs/api/errors/idempotency_conflict` |

## When it happens

An `Idempotency-Key` was reused, but the stored request it maps to conflicts with this one in a way that is not a clean replay.

## Example response

```json
{
  "type": "https://aishorty.com/docs/api/errors/idempotency_conflict",
  "title": "Idempotency conflict",
  "status": 409,
  "detail": "This idempotency key conflicts with an earlier request.",
  "instance": "urn:request:req_01J9Z8ABCDEFGH0123456789",
  "code": "idempotency_conflict",
  "request_id": "req_01J9Z8ABCDEFGH0123456789"
}
```

## How to fix it

Use a fresh `Idempotency-Key` for a genuinely new request; reuse a key only to safely retry the exact same call.

## Related errors

- [idempotency_key_reused](/docs/api/errors/idempotency_key_reused) — Idempotency key reused (HTTP 422)
- [idempotency_in_progress](/docs/api/errors/idempotency_in_progress) — Idempotency request in progress (HTTP 409)