Negotiate format via headers, not path suffixes.
Section: Naming conventions
Avoid format suffixes in paths
text
text
Prefer: GET /reports/123
Avoid: GET /reports/123.jsonExplanation
Content negotiation and media types are usually cleaner than path-based format suffixes.
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.
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.