Last Updated: February 25, 2016
· jjperezaguinaga
Me 180x180

REST HTTP Verbs in one image


REST is a beautiful and simple way to represent the resources you have in your application; as a Front End Engineer, REST provides me a layer to communicate statelessly with my resources without having to worry about anything else. As a Back End Engineer, I can describe the behaviour of my system in resources and even mock them in the meantime for Front End Engineers so we can be in the same track how the application is being built.

Yet, I still see some developers using things like $.post(...) to perform a delete call inside a system. According to the Richardson Maturity Model, we are to use the proper HTTP Verbs in order to take advantage of the benefits of REST such as the idempotence of specific verbs (GET, PUT, DELETE) and catching.

For people that still need a clear example on when to use which specific HTTP verb, I'm leaving here a diagram with an easy to understand example for each of the basics HTTP verbs (OPTIONS and HEAD not covered). This comes from the free ebook Web API Design. Hope it helps!

REST Example

Say Thanks