API Design
May 19, 2019

API Design Image


First and foremost I'd like to reference everything in this article. Please read that for all the details. There are 3 things I would highlight if we were working together.


Almost all routes should represent an entity or a collection of entities. This means pagination and appropriate filter abilities for the client to use. If the client requests an entity be updated, the entity should be in the response. The reference above covers this topic well.

Bulk Operations

Bulk operations are not covered in the article above. My preference is the following:

POST /route

[{ids: [1, 3], status: 0}, {ids: [2], status: 1}]

This should return the modified entities so that the client can merge the data into it's state.


The last topic, which I'd like to highlight is errors. Use 4xx http status for client issues and 5xx for server side issues. Most js client libraries automatically resolve 4xx and 5xx http status codes as errors. So in my opinion using the literally correct http status code is not a hard requirement. The response signature should be:

  "message" : "Something bad happened :(",
  "description" : "More details about the error here"
  "message" : "Validation Failed",
  "errors" : [
      "field" : "first_name",
      "message" : "First name cannot have fancy characters"
       "field" : "password",
       "message" : "Password cannot be blank"

Most of the time the client should be able to put the message field directly into the interface. This means it should be human readable and understandable to the end user. The message should also be < 200 characters.


  • JSON keys should never have a space
  • If a request sends Accept: application/json header, the backend should respectfully respond in kind.

Great! Now we can work together!

Get updates