Skip to main content
Networks drop answers. If a POST /v1/chars times out, you can’t tell whether the character was created. Send an Idempotency-Key header and retry with the same key: you get the original answer, and nothing is created twice.
Every POST accepts the header. The rules:
  • A key is 8 to 255 visible ASCII characters. A UUID or your own record id works well.
  • Keys belong to the API key that sent them, and are kept for 24 hours.
  • The same key with the same body, within 24 hours, returns the first status and body again with the header Idempotent-Replayed: true.
  • The same key with a different body is refused with 422. Bodies are compared by content, so key order does not matter.
  • If the first request is still running, a repeat gets 409. Wait and retry.
  • A 5xx answer is not stored, so retrying with the same key runs the request again.