Restful Web Apis ✪

REST brought this back to UserInterface along with a cheerful 200 OK status code. The Update

This was a , a standard HTTP method meant for retrieving data. REST picked up this request. REST didn't care that UserInterface had asked for Product #99 just a second ago. REST didn't know who UserInterface was, and didn't need to know. RESTful Web APIs

Add more technical detail on (POST, PATCH, DELETE) REST brought this back to UserInterface along with

{ "id": 101, "name": "SuperWidget", "price": 29.99, "status": "in-stock" } Use code with caution. Copied to clipboard REST didn't care that UserInterface had asked for

UserInterface sent a message out across the web highway: GET /products/101 The Journey

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: