About HTTP Method Reference & REST Verbs Guide
Technical reference and architectural comparison matrix for all standard HTTP request methods (GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS, TRACE, CONNECT) defined in RFC 9110 and RFC 5789. Inspect safety properties, idempotency guarantees, request/response body constraints, and code snippets.
Key Capabilities & Features
- Side-by-side comparison of all 9 core HTTP methods plus WebDAV extensions
- Safety and idempotency matrix indicating state mutation guarantees
- Cacheability indicators and payload body constraints (Request & Response)
- RESTful API architecture best practices and common design pitfalls
- Ready-to-use JavaScript fetch() and cURL execution snippets
How to Use HTTP Method Reference & REST Verbs Guide
Choose HTTP Verb
Select GET, POST, PUT, PATCH, DELETE, or OPTIONS.
Inspect Properties
Verify whether the method is safe (read-only) or idempotent (repeatable).
Review API Guidelines
Check recommended HTTP response status codes and body requirements.
Copy Code Snippet
Copy working JavaScript fetch() examples directly into your project.
Privacy & In-Browser Execution Guarantee
100% Client-Side. Reference specifications execute in browser with zero telemetry.
Frequently Asked Questions
What makes an HTTP method idempotent?
An HTTP method is idempotent if the side-effect of making $N > 0$ identical requests is identical to making a single request. PUT and DELETE are idempotent; POST is not.
When should I use PATCH instead of PUT?
Use PUT when replacing the complete representation of an existing resource. Use PATCH when applying a partial modification or updating specific attributes of a resource.