Let clients opt into embedded relationships.
Section: Path vs query parameters
Use includes for related resources
http
http
GET /orders/ord_123?include=customer,itemsExplanation
Optional includes can reduce round trips while keeping the base response lightweight.
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 Path vs query parameters
Put resource identity in the path
Use the path for the primary resource being addressed.
Use query parameters for filtering
Filter a collection with query fields.
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.