Member-only story
How I Design APIs As Senior Developer For Better Results
The decisions I make before writing a single line of API code
Bad developers do not write most bad APIs. Rushed developers do.
I know because I have built a few of them. And one of them still runs in production and requires constant rewriting.
Last quarter I reviewed the Orders API behind our new mobile app. At a glance, it looked fine. But once I read it properly, I found serious issues in it.
I want to walk you through how I redesigned it. The first few decisions are the basic ones most of us already know.
But the others are often ignored. That is exactly where bad API design starts to hurt.
Non-medium members click here to read for free.
The Problem With the Current API
Here is what the API looked like when it reached me:
And the response from /getOrderById:









