A plain-English guide
Idempotency
Designing a request so that repeating it does not create the same intended result more than once.
What it means in practice
A system may attach a unique key to an action and recognize later attempts using the same key. This is separate from refusing all retries: retries can be necessary when a network response is lost even though the original action succeeded.
An everyday example
A checkout request times out after an order is accepted. Retrying with the same action identity lets the system return the existing outcome instead of creating a second order.
Why it matters
Connections sometimes retry after a timeout. A safe retry should not create a duplicate payment, order or customer action.

