RESTful API Design Quotes

“Here are a couple of simple, practical tricks to determine if a service is not RESTful: If the name of the service is a verb instead of a noun, the service is likely RPC and not RESTful. If the name of the service to be executed is encoded in the request body, the service is likely RPC and not RESTful. If the back-button in the web-application does not work as expected, the service is not stateless and not RESTful. If the service or website does not behave as expected after turning cookies off, the service is not stateless and not RESTful.”
― Matthias Biehl, RESTful API Design: Best Practices in API Design with REST

“The Richardson Maturity Model can be used for determining the degree to which services are RESTful. The following levels are defined: Level 0: Services use an RPC style. Level 1: Services expose resources. Larger services are broken down into resources. Level 2: Services use HTTP methods correctly. Services use HTTP infrastructure efficiently. Level 3: Hypermedia is used according to HATEOAS. The service is self-documenting and flexible.”
― Matthias Biehl, RESTful API Design: Best Practices in API Design with REST

“Secure and Compliant The API needs to ensure that it can only be accessed by authenticated and authorized consumers. The API does not leak internal information. The API is compliant with best practices and with security regulations.”
― Matthias Biehl, RESTful API Design: Best Practices in API Design with REST