Published in


Should APIs use 404 as an error code?

The humble 404 error, so familiar on the web, is a problem for an API

Ever since I was first introduced to a web browser, I was familiar with the 404 error. It’s the first thing you learn, the first error code you find — because pretty much everyone makes spelling mistakes from time to time.

The definition of the 404 error can be traced back to the earliest web standards including RFC 1945, which is part of the IETF’s standards process. Seems authoritative.




Everything connected with Tech & Code. Follow to join our 900K+ monthly readers

Recommended from Medium

ThreeFold, Protocol.Love, Soulfie API & Our World Meeting/Collaboration

My journey into Software Engineering

How to improve your Messenger bot for pizza ordering and delivery

Project #5: OLED Display Using Adafruit SSD1306 on Arduino IDE

Data Structures and Algorithms Every Python Programmer Should Know (Part II)

AWS KMS — Concepts and Hands on Part 1

ASP.NET Core Google Authentication

Debugging Targets of

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ted Spence

Ted Spence

Software development management, focusing on analytics and effective programming techniques.

More from Medium

It’s Time to Redefine TDD

Do you commit frequently enough?

Cardinal Pull Request Mistakes Developers Keep On Making

The 7 principles of software testing