HTTP Method Reference
Complete reference guide for all HTTP methods — GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS. Each method includes its semantics, safe/idempotent/cacheable properties, common use cases, success and error status codes, and copy-ready request examples. Search, filter by method, and expand any card for full details. No signup required.
Interactive reference for all HTTP methods — GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS. Click any method card to expand its full semantics, use cases, status codes, and request examples.
Why Use Our HTTP Method Reference?
The fastest way to look up HTTP method semantics, use cases, and status codes
Instant Search Across All HTTP Methods
Our HTTP method reference lets you search by method name, description, or use case in real time. Find exactly what you need — whether you're looking for idempotency rules, status codes, or request body requirements.
Expandable Cards with Full Semantics
Each HTTP method card expands to show complete semantics: safe/idempotent/cacheable properties, common use cases, request body requirements, success and error status codes, and copy-ready request examples.
Secure HTTP Method Reference Online
Our HTTP method reference runs entirely in your browser — no data is sent to any server. All reference data is loaded locally, so the tool works completely offline once the page is loaded.
HTTP Method Reference — No Installation, 100% Free
Use our HTTP method reference directly in any browser with no downloads, no account, and no ads. Filter by method, expand all cards at once, and copy request examples — completely free forever.
Common Use Cases for HTTP Method Reference
From API design to debugging — http method reference for every workflow
REST API Design
Use our HTTP method reference to choose the correct method when designing REST APIs. Understand when to use PUT vs PATCH, or POST vs PUT, to build semantically correct and predictable endpoints.
API Integration & Debugging
Developers integrating third-party APIs use our http method reference to understand what each method does and what status codes to expect. Quickly look up whether a method is idempotent before retrying failed requests.
Backend Development
Backend engineers use our HTTP method reference to implement correct route handlers. Understand which methods require a request body, which should return 201 vs 200, and which are safe to cache.
Frontend & Client Development
Frontend developers use our http method reference to write correct fetch and Axios calls. Know when to use POST for form submissions, GET for data fetching, and DELETE for resource removal.
API Documentation Writing
Technical writers use our HTTP method reference to document APIs accurately. Reference the correct semantics, idempotency rules, and status codes for each method in your OpenAPI or Swagger docs.
Learning & Interview Prep
Developers learning REST or preparing for technical interviews use our http method reference to master HTTP semantics. Understand safe vs idempotent methods, CORS preflight, and the difference between PUT and PATCH.
Understanding HTTP Methods
How HTTP methods define the semantics of API requests
What are HTTP Methods?
HTTP methods (also called HTTP verbs) define the action to be performed on a resource identified by a URL. They are a core part of the HTTP protocol and the foundation of RESTful API design. The most commonly used methods are GET (retrieve), POST (create), PUT (replace), PATCH (partial update), and DELETE (remove). Additional methods like HEAD, OPTIONS, CONNECT, and TRACE serve specialized purposes. Our HTTP method reference covers all standard methods with their semantics, use cases, and request/response details.
How Our HTTP Method Reference Works
- Browse or Search: Use the search bar to find any http method by name, description, or use case. Or click a method filter pill (GET, POST, PUT, etc.) to jump directly to that method. All filtering runs instantly in your browser.
- Expand for Full Details:Click any method card to expand it and see the complete reference — safe/idempotent/cacheable properties, use cases, request body requirements, success and error status codes, and HTTP request examples. Use “Expand All” to open every method at once.
- Copy Request Examples: Each method includes copy-ready HTTP request examples. Click the Copy button on any example to copy it to your clipboard for use in your API client, documentation, or code.
Key HTTP Method Properties Explained
- Safe: A method is safe if it does not modify server state. GET, HEAD, and OPTIONS are safe — they only retrieve information. POST, PUT, PATCH, and DELETE are not safe because they change data on the server.
- Idempotent: A method is idempotent if making the same request multiple times produces the same result as making it once. GET, HEAD, OPTIONS, PUT, and DELETE are idempotent. POST is not — sending the same POST twice typically creates two resources.
- Cacheable: A method is cacheable if its responses can be stored and reused. GET and HEAD responses are cacheable by default. POST responses are only cacheable with explicit Cache-Control headers. PUT, PATCH, and DELETE responses are not cacheable.
- Request Body: Some methods carry a request body (POST, PUT, PATCH), while others do not (GET, HEAD, DELETE, OPTIONS). Sending a body with GET is technically allowed but strongly discouraged and often ignored by servers.
PUT vs PATCH — When to Use Each
PUT replaces the entire resource — you must send all fields, and any field not included will be set to null or its default value. Use PUT when you want to fully replace a resource. PATCH applies a partial update — only the fields you send are changed, and all other fields remain unchanged. Use PATCH when you only need to update one or a few fields. In practice, most modern REST APIs prefer PATCH for updates because it is more efficient and less error-prone than sending the full resource on every update.
Related Tools
JSON to YAML
Convert JSON to YAML format instantly - Free online JSON to YAML converter
XML to YAML
Convert XML to YAML format for configuration migration - Free online XML to YAML converter
CSV to YAML
Convert CSV spreadsheet data to YAML format - Free online CSV to YAML converter
TSV to YAML
Convert TSV tab-separated data to YAML format - Free online TSV to YAML converter
Frequently Asked Questions About HTTP Method Reference
Common questions about HTTP methods, REST semantics, and API design
An HTTP method reference is a guide to the standard HTTP verbs — GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS — that define the action to perform on a resource. Our http method reference covers each method's semantics, safe/idempotent properties, use cases, status codes, and request examples.
PUT replaces the entire resource — you must send all fields, and any field not included will be overwritten with null or its default. PATCH applies a partial update — only the fields you send are changed. Use PUT for full replacements and PATCH for partial updates. Most modern REST APIs prefer PATCH for efficiency.
An idempotent method produces the same result whether you call it once or ten times. GET, HEAD, OPTIONS, PUT, and DELETE are idempotent. POST is not — sending the same POST request twice typically creates two separate resources. Idempotency is important for safe retry logic in distributed systems.
A safe HTTP method does not modify server state — it only reads data. GET, HEAD, and OPTIONS are safe. POST, PUT, PATCH, and DELETE are not safe because they create, update, or delete data. Safe methods can be called freely without side effects.
Use POST when the server determines the new resource's URI (e.g. POST /users creates a user and the server assigns the ID). Use PUT when the client specifies the full URI of the resource (e.g. PUT /users/42 replaces user 42). POST is not idempotent; PUT is.
A CORS preflight request is an OPTIONS request that browsers automatically send before cross-origin requests with custom headers or non-simple methods. The server responds with Access-Control-Allow-Methods and Access-Control-Allow-Headers to indicate whether the actual request is permitted.
Yes. Our HTTP method reference runs entirely in your browser — all reference data is loaded locally with no server requests. Your searches and interactions never leave your device. The tool works completely offline once the page is loaded.
Yes, our HTTP method reference is 100% free with no signup, no account, no usage limits, and no advertisements. Use it as many times as you need — completely free, forever.