What Does Idempotent Mean in HTTP? GET, PUT, DELETE Explained

An idempotent HTTP method produces the same result no matter how many times it's repeated. Learn which methods are idempotent and why it matters for retries.

Published September 20, 2026

An idempotent request has the same effect on the server whether you send it once or many times. GET, PUT and DELETE are idempotent; POST is not.

The concept

Idempotent does not mean the response is identical, only that the server state ends up the same. Deleting a user twice leaves the user deleted both times (the second reply may be 404).

This matters for retries: when a network call times out, you can safely resend idempotent requests, but retrying a POST could create duplicates.

Repeat the request

PUT /users/7 {name:'Ada'} ×3
user 7 = Ada (same state)
POST /orders {item:1} ×3
3 orders created

Practical examples

Make a POST safe to retry

Send a unique key; the server stores the result and returns it again on repeats.

POST /payments
Idempotency-Key: 8f14e45f-ceea-4673

{"amount": 100}

Method cheatsheet

GET     safe, idempotent
HEAD    safe, idempotent
PUT     idempotent (replace)
DELETE  idempotent
POST    not idempotent
PATCH   not guaranteed

Not idempotent PUT trap

// counter += 1 is NOT idempotent, even if sent via PUT
PUT /counter { increment: 1 }

Common mistakes

  • Retrying POST requests blindly.
  • Designing PUT as 'add one to counter'.
  • Confusing idempotent with safe — DELETE is idempotent but not safe.

Key takeaways

  • Same effect when repeated.
  • GET/PUT/DELETE yes, POST no.
  • Use idempotency keys for payments.

FAQ

Is PATCH idempotent?

Not guaranteed; it depends on whether the patch sets values or applies increments.

What is a safe method?

One that does not change state at all, such as GET and HEAD.

More HTTP articles