🔗 RESTful API guidelines

RESTful API s started being widely adopted for systems interoperability and integration in the mid-2000s, maybe earlier.

Two decades later, many API s in production today, that claim to be “RESTful”, violate basic REST principles, creating confusion, frustration, and unnecessary complexity.

Take for instance:

• POST /accountSearchByNumber
• POST /accountSearchByLogin
• POST /DeleteEvent
• Lack of security, either at the protocol level or allowing data access to users/personas not related to it.
• Operation in the request body.
• Inconsistent Resource Naming.
• Returning 200 OK when there was a validation error or an exception.
• Often times, level 0 from the Richardson Maturity Model code.
• No documentation.

This blog post is revised regularly to keep the recommendations for building scalable and secure REST API s up-to-date.