Representational State Transfer
as an architectural approach to designing web services. REST is an architectural style for building distributed systems based on hypermedia. REST is independent of any underlying protocol and is not necessarily tied to HTTP. However, most common REST API implementations use HTTP as the application protocol, and this guide focuses on designing REST APIs for HTTP.
HTTP.
is a URI that uniquely identifies that resource. For example, the URI for a
particular customer order might be: https://adventure-works.com/orders/1
GET ,post delete,patch,put
nouns
GET https://adventure-works.com/products/10?fields=productImage HTTP/1.1 Range: bytes=0-2499
web APIs that expose a large number of small resources. Such an API may require a client application to send multiple requests to find all of the data that it requires
returns HTTP status code 200 (OK).
It should return 404 (Not Found).
It returns HTTP status code 201 (Created), the response body contains a representation of the resource.
The web server should respond with HTTP status code 204, but that the response body contains no further information.