What does idempotent mean for an HTTP method?

An idempotent method produces the same server state whether you send the request once or many times. GET, PUT and DELETE are idempotent; POST and PATCH are not, because repeating them can create duplicates or compound changes.

Which HTTP methods are safe?

Safe methods are read-only and must not change server state: GET, HEAD, OPTIONS and TRACE. POST, PUT, PATCH, DELETE and CONNECT are not safe because they are intended to cause effects.

Is this reference loaded from a server?

No. The full table and the search run entirely in your browser — nothing is fetched and nothing you type is uploaded.

HTTP Methods Reference

GET, POST, PUT and the rest — safe, idempotent, cacheable.

HTTP methods reference

A quick, searchable table of the HTTP methods defined by RFC 9110 — GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, TRACE and CONNECT — and the properties that matter when designing an API: whether each method is safe, idempotent, cacheable and whether it carries a request body.

Search by method name or by a property like idempotent to filter the table. Everything runs in your browser; nothing is uploaded.