API Status Codes on a Merry Go Round - Which One Stops it and Why?

I was thinking of some fun questions to put out on the MoT Twitter account when I came up with “3 API status codes are on a merry go round. One of them stops it. Which one and why?”

In true tester style, once I started talking to @friendlytester and @testingchef about which 3 status codes it should be, I had too many fun options! So, I decided to choose 3 for Twitter and a different 3 for The Club.

So for you wonderful Club members:

3 API status codes are on a merry go round - 418, 417 and 429. One of them stops it. Which one and why?

3 Likes

Here’s my answer (click to reveal):

417!

  • 418 can be used for anything because it’s a teapot and will often be implemented for fun.
  • 429 is Too many requests, which means some requests were successful therefor not stopping ‘all’ of them.
  • 417 means there is an expected header field missing/doesn’t meet the standards, which stops the request with 417 Expectation failed"

I really enjoyed this game! :stuck_out_tongue:

2 Likes

The status codes I used in the Tweet if anyone wants to try those :grin:

2 Likes