REST API Resource Naming and URL Design/Expose canonical resource paths

Each resource should have an obvious direct URL.

Section: Naming conventions

Expose canonical resource paths

text
text
/orders/{orderId}
/order-items/{itemId}
Explanation

Even if a resource is reachable through a nested route, it often helps to expose a canonical direct path for the item itself.

Learn the surrounding workflow

Compare similar commands or jump into common fixes when this command is part of a bigger troubleshooting path.

Related commands

Same sheet · prioritizing Naming conventions
Use consistent casing in paths
Pick one URL style and use it consistently.
OpenIn sheettextsame section
Avoid format suffixes in paths
Negotiate format via headers, not path suffixes.
OpenIn sheettextsame section
Name relationships clearly
Make related collections obvious.
OpenIn sheettextsame section
Keep nesting shallow
Prefer one or two levels of depth.
OpenIn sheettextsame section
Put resource identity in the path
Use the path for the primary resource being addressed.
OpenIn sheethttp1 tag match
Use query parameters for filtering
Filter a collection with query fields.
OpenIn sheethttp1 tag match