← Integration Engineering
Integration Engineering

Status Codes That Matter: The Number Tells You Whose Fault It Is

29 Sept 2026·3 min read

Every API reply starts with a three-digit status code. It takes one second to read, and it points you in the right direction.

The first digit is most of the answer

  • 2xx: it worked.
  • 4xx: something is wrong in your request. Your side.
  • 5xx: the other server had a problem. Their side.

The ones you will see every week

  • 200 / 201: it worked. 201 means something new was made.
  • 400 Bad Request: your data is wrong. Check field names and types.
  • 401: the server does not know you. The token is missing, wrong or expired.
  • 403: it understood you, but will not allow this. A fresh token with the same access will not fix it.
  • 404: that address or record does not exist.
  • 429 Too Many Requests: you are calling too fast. Wait, then try again.
  • 500 / 503: their server has a problem. Retry later, and do not change your code yet.

The difference that decides your retry logic

Most 4xx codes fail again if you send the same thing, so change something first. 429 is the exception: wait, then retry. A 5xx might work next time. But when a request creates something, a 5xx or no reply does not prove nothing happened.

How I learned thisMy LinkedIn scheduler could post twice: if LinkedIn made the post but the reply got lost, a retry made it again. Now a clear 4xx keeps the post in the queue, and a 5xx or no reply parks it and emails me to check.
Do this in 60 secondsOpen https://api.github.com/users/ followed by a made-up name in your browser. You will see "Not Found". Say whose side that is on.
Today’s AI angleGive your AI agent the status code with every tool result. Tell it the rule: 4xx means change something, 5xx and 429 mean wait and retry, and never retry a create blindly.
Status Codes That Matter: The Number Tells You Whose Fault It Is · Ali Huzaifa