O'Reilly logo
  • Dan Sanders thinks this is interesting:

It is typically appropriate to return only a few attributes or pieces of data when responding with a collection, such as in the preceding example. Now the caller can use the URI to query a specific resource to retrieve all attributes of that resource. For example, the Tasks collection response (as just shown) might contain only the Task’s Id and a URI to fetch the Task resource. But when calling GET to get a specific Task, the response might include TaskCategory, DateCreated, ...


Cover of ASP.NET Web API 2: Building a REST Service from Start to Finish


get resource collections vs get single resource