As mentioned, REST is a resource-centric architectural style that makes use of URIs and HTTP verbs (for example, GET, PUT, POST, DELETE, and PATCH) in order to perform actions against a given (unique) resource. This is in contrast to RPC-based protocols, such as SOAP, gRPC, and even GraphQL, where the action is explicit in the payload of the message. For example, a HTTP GET request against a http(s)://<server>/customers URI implies listing all customers available in the /customers resource.

Doing a HTTP POST call against the same resource means creating a new customer record, details of which should be provided as part of the HTTP payload.

The following is a process view representation of REST extracted from Fielding's dissertation. ...

Get Enterprise API Management now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.