A scannable reference for every HTTP request method — GET, POST, PUT, PATCH, DELETE and the rest, plus WebDAV — showing at a glance whether each one is safe, idempotent and cacheable, if it takes a body, and a typical example. In your browser, free.

Every standard HTTP request method and its semantics, side by side. Everything runs in your browser from a built-in reference — nothing is sent to the server.

Method Purpose Safe Idempotent Cacheable Body Typical use
No method matches your search.
Try a different name or term — for example PATCH, idempotent or cache.
Yes No Conditional Optional Discouraged

About HTTP Methods

This HTTP methods reference puts every standard request method — GET, HEAD, POST, PUT, PATCH, DELETE, CONNECT, OPTIONS and TRACE — plus the common WebDAV extensions into one scannable table. For each method it answers the questions developers actually reason about: is it safe, is it idempotent, is it cacheable, does it carry a request body, and what does a typical use look like.

Those three semantic properties drive real design decisions. Safe methods are read-only and can be prefetched freely; idempotent methods can be retried after a network failure without side effects, which is exactly what proxies and HTTP clients assume; and cacheability determines whether responses may be stored and reused.

Search matches method names, properties and use cases — PATCH, idempotent and cache all filter the table — and a group toggle separates the standard methods from the WebDAV set. Each method name copies to the clipboard in one click.

How to use HTTP Methods

  1. Scan the table to compare methods across the Safe, Idempotent, Cacheable and Body columns.
  2. Search by name, property or use case — for example PUT, idempotent or upload.
  3. Switch between the Standard and WebDAV groups to include or exclude the extension methods.
  4. Hover the column tooltips for a plain-language definition of each property.
  5. Click the copy button to grab a method name for your API spec or test.

Frequently asked questions

Safe means the request does not change server state at all — GET and HEAD are read-only. Idempotent means repeating the identical request has the same effect as sending it once — DELETE is idempotent but not safe, because the first call does change state.

PUT replaces the entire resource with the body you send and is idempotent. PATCH applies a partial modification — only the fields you include change — and is not guaranteed idempotent. Use PUT for full replacements and PATCH for targeted updates.

Because clients, proxies and SDKs automatically retry idempotent requests after timeouts or dropped connections. A non-idempotent POST retried blindly can create duplicate orders or records, which is why payment APIs pair POST with idempotency keys.

GET and HEAD responses are cacheable by default. POST responses may be cached only when explicit freshness headers allow it, which is rare in practice. The other methods are not cacheable — their responses must not be stored and reused.

WebDAV extends HTTP for remote file management, adding methods such as PROPFIND, MKCOL, COPY, MOVE, LOCK and UNLOCK. You’ll meet them when working with WebDAV servers, calendar/contact protocols built on them, or network drive integrations.

Yes. The whole table is free and runs in your browser from a built-in dataset — searching and filtering send nothing to the server.

Need help?
Found an issue with this tool? Let our team know.
Report an issue

Add this free tool to your own website — copy and paste the code below.