Representational State Transfer
An architectual structuring
A resource has an identifier, which 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, Put, Patch, and Delete
A URI must represent an object, uniquely and permanently One of the most fundamental philosophies behind a URI is that it represents a data object on the Internet. The URI must be unique so that it is a one-to-one match – one URI per one data object. https://css-tricks.com/guidelines-for-uri-design/
This same website also mentions it’s a good idea to make it something user friendly; short, to the point, and recognizable.
https://adventure-works.com/orders // Good
https://adventure-works.com/create-order // Avoid
Being ‘chatty’ basically means there are too many call back requests of the network. When calling for multiple pieces of information, they can be bundled instead of being sparsed out into singular requests. It is a bad thing that ends up bogging down the system by tying it up.
It retrieves a representation of the resource at the specified URI. The body of the response message contains the details of the requested resource.
404 not found
Creates a new resource at the specified URI. The body of the request message provides the details of the new resource. Note that POST can also be used to trigger operations that don’t actually create resources.
It removes the resource at the specified URI.