Random HTTP Method Generator

Generates a random real HTTP request method (GET, POST, PUT, and so on) — seven from the RFC 9110 standard plus PATCH from RFC 5789 — along with its standard meaning, useful for teaching or test scenarios.

Seed (optional)

The same word, at the same settings, gives the same result. It goes into the address when you generate, so a copied link opens with the word in the box. A seed is for repeatability, not secrecy.

Don't repeat what I've already seen

Your result will appear here.

What this generator does

Draws a real HTTP method together with what the specification says it means. The distinction that matters in practice is safety and idempotency: GET and HEAD must not change anything, PUT and DELETE must be repeatable without further effect, and POST guarantees neither.

What you'll get

This generator draws from a hand-checked list of 8 entries. Here is a spread of 6 of them, so you can see the style before you generate:

GET — retrieve a resource
POST — create a resource or submit data
PUT — replace a resource entirely
DELETE — remove a resource
HEAD — like GET, but headers only, no body
OPTIONS — ask what methods/operations are supported

A fixed sample of the list, not a live draw — your own results are picked at random from all 8, without repeating until the list runs out. RFC 9110 HTTP request methods (public/factual technical standard). Last reviewed 2026-09-01.

How to use this tool

Press generate for a method.
Generate again for another one.

Understanding the controls

Seed (optional): For as long as the generator is unchanged, a word here brings back the same method and meaning out of the eight listed. Leave it blank for a fresh one. The word goes into the page address when you draw, so sending the link sends the word: the same method comes back when the button is pressed.

Common use cases

Teaching HTTP concepts
API test-scenario planning
Documentation examples

Limitations and good to know

TRACE is left off the list. It is part of the RFC 9110 method set alongside seven of the eight offered here (PATCH is defined separately, in RFC 5789), but it is routinely disabled on real servers, so including it would be a less useful example than the others.

Practical tips

If a request can be safely retried after a timeout, it should be idempotent. That single property decides more API design arguments than any naming convention.

Entries are chosen with your browser's cryptographic random number generator, so every entry on the list is equally likely. How Generate Random works.