HTTP Methods Reference
Complete reference for HTTP methods with safe/idempotent properties, use cases, status codes, and request examples.
9 methods
Retrieves a resource. Should never modify server state. Responses can be cached.
Submits data to create a new resource or trigger an action. Not idempotent — calling it twice creates two resources.
Replaces a resource entirely with the provided representation. Idempotent — calling it multiple times has the same effect.
Applies a partial update to a resource. Only the provided fields are changed. May or may not be idempotent depending on implementation.
Removes a resource. Idempotent — deleting an already-deleted resource should return 404 or 204, not an error.
Same as GET but returns only headers, no body. Used to check resource existence or metadata without downloading the full response.
Returns the HTTP methods supported by the server for a URL. Browsers send this automatically as a CORS preflight request.
Establishes a tunnel to the server identified by the target resource. Used by HTTP proxies to set up SSL tunnels.
Performs a message loop-back test along the path to the target resource. Useful for debugging but often disabled due to XST attacks.
What Is HTTP Methods Reference?
A complete reference for all standard HTTP methods (verbs) defined in RFC 7231 and related specs. Each entry covers safe/idempotent properties, typical use cases, expected status codes, and a concrete request example — everything you need to design RESTful APIs correctly.
How to Use
- Search by method name or description keyword
- Filter by safe, idempotent, or has-body properties
- Expand any method to see use cases, status codes, and an example request
Features
- All 9 standard HTTP methods covered
- Safe and idempotent property indicators
- Typical success status codes per method
- Concrete request examples for each method
FAQ
What does "safe" mean for an HTTP method?
A safe method does not modify server state. GET, HEAD, OPTIONS, and TRACE are safe. Browsers and caches can freely repeat safe requests without side effects.
What does "idempotent" mean?
An idempotent method produces the same result whether called once or many times. GET, PUT, DELETE, HEAD, OPTIONS, and TRACE are idempotent. POST is not — calling it twice creates two resources.
When should I use PUT vs PATCH?
Use PUT to replace an entire resource. Use PATCH to update specific fields. PUT requires sending the full resource representation; PATCH only sends the fields you want to change. PATCH is more bandwidth-efficient for large resources.
What is the difference between POST and PUT?
POST creates a resource at a server-chosen URL (e.g., /users → /users/42). PUT creates or replaces a resource at a client-specified URL (e.g., PUT /users/42). POST is not idempotent; PUT is.