Every request contained everything necessary to understand it: the target ( /products/101 ) and the intent ( GET ). The Resource
Create a story based on a (e.g., shopping cart, user authentication)
UserInterface sent a message out across the web highway: GET /products/101 The Journey RESTful Web APIs
REST hurried to the Warehouse Server. In DataVille, everything was a —a noun, not a verb. REST asked for the representation of Product 101 . The Response The Server handed REST a small, clean JSON document:
In DataVille, RESTful APIs make sure that every interaction is smooth, standard, and fast, proving that sometimes, not remembering the past makes for a better future. If you liked this, I can: REST asked for the representation of Product 101
Add more technical detail on (POST, PATCH, DELETE)
Later, UserInterface needed to change the price of the SuperWidget. It sent a new request: PUT /products/101 with the new data. It sent a new request: PUT /products/101 with the new data
{ "id": 101, "name": "SuperWidget", "price": 29.99, "status": "in-stock" } Use code with caution. Copied to clipboard