Prefer one or two levels of depth.
Section: Naming conventions
Keep nesting shallow
text
text
Better: /orders/{orderId}/items
Avoid: /customers/{customerId}/orders/{orderId}/items/{itemId}/notesExplanation
Deeply nested URLs become harder to maintain, document, and cache.
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.
Avoid format suffixes in paths
Negotiate format via headers, not path suffixes.
Expose canonical resource paths
Each resource should have an obvious direct URL.
Put resource identity in the path
Use the path for the primary resource being addressed.