Return only needed fields.
Section: Path vs query parameters
Use query parameters for field selection
http
http
GET /users/123?fields=id,name,emailExplanation
Sparse fieldsets can reduce payload size and overfetching in large representations.
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 includes for related resources
Let clients opt into embedded relationships.
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.