Helps developers recall the semantics and applicability of HTTP request methods such as GET, POST, PUT, PATCH, DELETE, and OPTIONS while designing or debugging web APIs.
Runs locally in your browserHTTP methods define the intended operation for a request. Core methods include GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, and PATCH; extensions such as WebDAV add others.
| Number | Method | Description |
|---|---|---|
| 1 | GET | Retrieve a representation of the target resource. |
| 2 | HEAD | Retrieve the same headers as GET without a response body. |
| 3 | POST | Submit data for processing, often creating a resource or triggering an operation. |
| 4 | PUT | Create or completely replace the state of the target resource. |
| 5 | DELETE | Remove the target resource. |
| 6 | CONNECT | Establish a tunnel to the target, commonly through an HTTP proxy. |
| 7 | OPTIONS | Report communication options supported by the target resource or server. |
| 8 | TRACE | Perform a diagnostic loopback of the received request; often disabled for security. |
| 9 | PATCH | Apply partial modifications to the target resource. |
| 10 | MOVE | WebDAV method that moves a resource to the URI in Destination. |
| 11 | COPY | WebDAV method that copies a resource to the URI in Destination. |
| 12 | LINK | Obsolete method proposed for establishing links between resources. |
| 13 | UNLINK | Obsolete method proposed for removing links between resources. |
| 14 | WRAPPED | Experimental method from the HTTP Extensions Framework; it is not part of core HTTP. |
| 15 | Extension method | Extension methods can add semantics beyond the methods defined by core HTTP. |