Back to tools
REST Naming Validator
Validate REST API endpoint paths against naming conventions
About REST Naming Validator
REST Naming Validator lets you validate rest api endpoint paths against naming conventions.
Category: API.
Frequently asked questions
What are REST naming conventions?
▾
REST endpoints should use nouns (not verbs), plural resource names, lowercase kebab-case, and hierarchical paths. For example: GET /users/{id}/orders, not GET /getUserOrders.
Why avoid verbs in REST URLs?
▾
The HTTP method (GET, POST, PUT, DELETE) already expresses the action. Using verbs in the path like /getUser or /deletePost creates redundancy and breaks REST semantics.
When should I use query params vs path segments?
▾
Path segments identify resources (/users/123). Query params filter, sort, or paginate a collection (/users?role=admin&page=2). Avoid using query params to identify a specific resource.