There are lots of misconceptions about REST APIs. People think REST is about HTTP, and is not. That developer UX is important, but it will soon be dead.
Here we discuss our approach to REST over HTTP and the difficulties and special scenarios we have found and how we solved them.
6. REST over HTTPREST over HTTP
@dcerecedoByteflair
Components
URIs
Verbs
StatusCode
Body
Headers
7. REST over HTTPREST over HTTP
@dcerecedoByteflair
Separate resource representation from
contextual data
Representation Body→
Contextualdata Headers→
8. REST over HTTPREST over HTTP
@dcerecedoByteflair
HTTP status code to inform client about the
result
2xx Ok→
Other Ko→
4xx Clienterror→
5xx Servererror→
9. REST over HTTPREST over HTTP
@dcerecedoByteflair
Use best matching HTTP Status codes
Add specific application error codes to error
responses