GET requests a resource representation at a URL. In REST, GET /products/123 returns the product, usually with more fields than a caller may need. Query parameters can filter fields, such as ?fields=name,price. section 6.4.1
A safe repeat
GET /orders/1 reads an order. Repeating the request does not change it, so GET is idempotent. section 6.4.1
Listing 6.1 REST Response
// REST Response: #A
{
"id": "123",
"name": "Salt & Vinegar Chips",
"price": 1.50,
"calories": 250,
"ingredients": [ "Potatoes", "Oil", "Salt"... ],
"manufacturer": { "name": "SnackCorp", "address": "123 Food Lane" }
}See a REST response with fields such as name, price, calories, and ingredients—a concrete example of receiving more than a narrow request may need. section 6.4.1
















