HTTP Methods

GET, POST, PUT, PATCH, DELETE & more — with semantics.

A reference of the HTTP request methods (verbs) — GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, CONNECT and TRACE — with what each does and its key properties: whether it's safe (read-only), idempotent (repeatable) and whether it carries a request body. Understand the difference between POST, PUT and PATCH for your REST API. Runs fully in your browser — no API.

How to use HTTP Methods

1. Open the list

   Launch this free HTTP methods reference to see every request verb and its semantics in one place.

2. Find a method

   Search for a method like GET, POST or PATCH, or just scan the short list.

3. Check the properties

   See at a glance whether a method is safe, idempotent and whether it carries a body.

4. Read the meaning

   Each method has a plain-English description of when and how to use it.

5. Design your API

   Use the right verb for each action — GET to read, POST to create, PUT/PATCH to update, DELETE to remove.

6. Copy a method

   Tap any method name to copy it for your code or API client.

Frequently asked questions

What are HTTP methods?

HTTP methods (also called verbs) tell the server what action to perform on a resource. The main ones are GET (read), POST (create), PUT (replace), PATCH (partially update) and DELETE (remove). Others include HEAD, OPTIONS, CONNECT and TRACE.

What is the difference between PUT and PATCH?

PUT replaces an entire resource with the data you send, while PATCH applies a partial update — only the fields you include change. PUT is idempotent (repeating it has the same effect); PATCH may not be.

What does 'safe' and 'idempotent' mean?

A 'safe' method (like GET or HEAD) only reads data and has no side effects. An 'idempotent' method (like GET, PUT or DELETE) can be repeated with the same result — sending it twice is the same as sending it once. POST is neither safe nor idempotent.

When should I use GET vs POST?

Use GET to retrieve data without side effects (it can be cached and bookmarked), and POST to send data that creates a resource or triggers processing. Never use GET for actions that change data.

Is this HTTP methods tool free?

Yes — it's completely free with no sign-up. The list runs in your browser from a built-in dataset, so there are no limits, no API keys and nothing is uploaded.

Which HTTP methods are used in a REST API?

A REST API typically maps GET (read a resource), POST (create), PUT (replace), PATCH (partially update) and DELETE (remove) onto its endpoints. GET and DELETE are idempotent, GET is safe, and POST is neither — this reference shows those properties for each method.

Can a GET request have a body?

By the HTTP spec a GET request may technically include a body, but it has no defined meaning and many servers, proxies and libraries ignore or reject it — so in practice GET requests don't carry a body. Use POST or PUT when you need to send data. This table shows which methods carry a body.

Related tools — Reference · Codes & Web

• HTTP Status Codes — Every HTTP response code (200, 301, 404, 500) with its meaning.
• HTTP Headers List — Common request & response HTTP headers, explained.
• HTML Entity Codes — HTML entities & symbol codes —  , ©, ®, →, ×, and more.
• ASCII Table — Full ASCII chart (0–127) with dec, hex, octal & binary values.
• Unicode Characters — Useful Unicode symbols with code points — copy any of them.
• DNS Record Types — A, AAAA, CNAME, MX, TXT & more — what each DNS record does.
• File Extensions & MIME Types — Common file extensions mapped to their MIME (media) type.
• Programming Language Extensions — File extensions for every programming language (.py, .js, .rs…).
• TLD List — Top-level domains — gTLDs & country-code TLDs explained.
• Mobile Network Codes (MCC/MNC) — MCC & MNC codes that identify mobile operators worldwide.
• Network Port Reference — 108+ TCP/UDP ports with a security rating & firewall rule generator.