REST Stands for representational state transfer, it’s essentially an architectural approach to designing web services
rest APIS are designed around resources which are objects data or services that can easily be accessed by clients
identifiers are urls that uniquely identify different resources,different urls might take you to different parts of a webpage or different resources From a site
the most common HTTPverbs getget, post, put, patch and delete
URIS should be based on nouns or resources And not verbs which are the operations on the resources
This is an example of a good versus a bad URI
https://adventure-works.com/orders // Good
https://adventure-works.com/create-order // Avoid
having a chatty API is when there are more requests that impose a huge load on a web server,This can send multiple requests to find all of the data requires and can overload the server.
a successful get request will return the status code of 200 or OK
when get requests are unsuccessful you will oftentimes get the most common error message which is 404 not found
If you have a successful post method it will create a new resource which returns the status code 201 or created
A successful delete operation will respond with the status code of 204 meaning no content. it indicates that that process has been successfully completed and the response contains no further information.