Complete HTTP verbs cheat sheet with features, usage, comparison, and REST API best practices
Zero Dependencies · Works Offline| Feature | GET | POST | PUT | PATCH | DELETE |
|---|---|---|---|---|---|
| Idempotent | ✅ | ❌ | ✅ | ❌ | ✅ |
| Safe | ✅ | ❌ | ❌ | ❌ | ❌ |
| Cacheable | ✅ | ❌ | ❌ | ❌ | ❌ |
| Request Body | Optional | Required | Required | Required | Optional |
| Semantics | Read | Create | Full Update | Partial Update | Delete |
| RFC | 9110 | 9110 | 9110 | 5789 | 9110 |
The HTTP Method Reference is a free online developer reference tool that provides complete documentation for all HTTP/1.1 and HTTP/2 request methods, including GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, and more. Each method includes semantic description, idempotency, safety, caching behavior, request body requirements, and detailed usage examples with a comparison table and REST API best practices. All content renders locally in your browser.
1. All HTTP method cards display on page load.
2. Use filter buttons to quickly find specific methods.
3. Check the comparison table for method differences.
4. Click "Copy Table" or "Download Reference" to export.
Developers reference HTTP method semantics and best practices when designing RESTful APIs to choose the correct verb.
Job seekers quickly review core HTTP method concepts for technical interviews.
Verify HTTP method usage conforms to specifications and best practices during API design reviews.
HTTP methods (also called HTTP verbs) define the operation semantics on resources. RFC 9110 (HTTP Semantics) defines core methods: GET, POST, PUT, DELETE, HEAD, OPTIONS, TRACE, CONNECT. RFC 5789 defines PATCH. Idempotency means making the same request multiple times produces the same result. Safety means the request doesn't modify server state. REST architecture requires correct HTTP method semantics—GET should have no side effects, PUT should be idempotent full replacement.
GET retrieves with URL params, cacheable; POST creates with body params, more secure, no length limit.
PUT replaces entire resource; PATCH updates only modified fields. PUT is idempotent; PATCH is not necessarily.
Same request once or multiple times produces the same result. GET, PUT, DELETE are idempotent; POST is not.
DELETE removes a resource. In REST APIs, DELETE /users/123 removes user 123. It's idempotent.
OPTIONS retrieves supported methods. Browsers send OPTIONS preflight requests for CORS.
HEAD returns only headers without body. Used to check resource existence without downloading content.