HTTP Request Methods

Reference of HTTP request methods: GET, POST, PUT, DELETE and more.

Look up a method

Search by method or purposeType a method name or what you want to do to jump straight to it.

Filter by category

0 methods

Good to know

Safe methodsGET, HEAD, OPTIONS and TRACE are safe: they must not change server state. Browsers and caches can call them freely.

IdempotentPUT, DELETE and safe methods are idempotent: calling them N times has the same effect as once. POST is not.

Body in GETThe HTTP spec does not forbid a request body on GET, but many servers and proxies ignore or reject it. Put parameters in the query string instead.

PATCH vs PUTPUT replaces the whole resource; PATCH applies a partial modification. Use PATCH when you only want to update a few fields.

Selected MethodPick a method from the list on the left.

Pick a method

no selection yet

Type a method or tap a row on the left to see its purpose here.

Method / Purpose0 of 0

Tool Introduction

HTTP request methods tell a server what action the client wants to perform on a resource. This reference covers the methods you will meet in real APIs, from the everyday GET and POST to WebDAV extensions and rare experimental verbs.

Search by name or purpose, filter by category, and click any row to see what it does and whether it is safe, idempotent or cacheable. Methods follow RFC 7231, RFC 5789 (PATCH) and RFC 4918 (WebDAV).