API Endpoint Name Generator
Generates an example REST-style API endpoint path (e.g. /api/v1/orders/{id}) — a full route example, distinct from a single URL slug, for API design practice or documentation.
What it builds, and how many ways
Each result is assembled to this shape: [version] + [resource] — one of 4 sentence patterns this generator uses.
- resource: 28 options
- sub: 7 options
- version: 4 options
Taken together those banks can be assembled 1,204 different ways, repeating after about 43.
{id} is left in place deliberately — it is part of the format rather than something the generator fills in.
Some results it can produce:
- /api/v1/reports
- /api/v2/events/{id}
- /api/v3/subscriptions/{id}/history
- /events/{id}/members
A fixed sample so this page stays the same between visits. Your own results are assembled at random, each slot filled independently and each press independent of the last, so the same result can come up twice — past the repeat figure above, seeing one twice is more likely than not.
How to use this tool
- Press generate for an endpoint path.
- Generate again for another one.
Common use cases
- API design practice
- Documentation/mockup examples
- Teaching REST conventions
Practical tips
- Name the resource, not the action — the HTTP method carries the verb, and putting one in the path duplicates it.
- Keep plurals consistent across the whole API; mixed conventions are a permanent low-level irritation.
Each part of the result is chosen independently with your browser's cryptographic random number generator, so every option in a bank is equally likely. How Generate Random works.