Page History

...

At a minimum, the GET /customers API should return all URIs related to each customer in the collection. However, perhaps a client wants to use this API as a way to provide visitors with a list of customers. If the client intends to display other customer properties (e.g., first and last name), then the client would need to make a GET /customers/{id} request for each URI. This could become a resource intensive process. It would be far better if the initial GET /customers request not only returned all the URIs , but also a along with partial resource object that objects which can be immediately consumed and used by the client. Here is an example of a resource object with one embedded resource:

...