URI Design Rules
Prefer stable, meaningful nouns.
Good examples:
GET /usersGET /users/42GET /users/42/ordersPOST /orders
Avoid RPC-style paths such as GET /getUsers, POST /createUser, or POST /deleteUser when standard HTTP semantics can express the operation.
Use plural collection nouns consistently. Path parameters normally identify a specific resource. Query parameters are better for filtering, sorting, pagination, projection, and optional retrieval behavior.
Do not put sensitive information such as passwords, access tokens, or secrets into URLs because URLs can be logged, cached, stored in browser history, or transmitted through intermediary systems.
URI Examples
Collection:
/usersRepresents a collection of user resources.
Member:
/users/42Identifies one user.
Nested relationship:
/users/42/ordersRepresents orders associated with user 42.
Filtering:
/users?role=adminQuery parameters modify collection retrieval.