Hard to get behind an argument on status codes being pointless when the article itself cites the usefulness of wisely chosen status codes, such as &quot;201 Created, 429 Too Many Requests, and 503 Service Unavilable&quot;.<p>I&#x27;ve created and used many a RESTful API and can vouch the ones that just return 200 even in cases of error are a big pain in the neck.<p>This is usually done (IMO) as a shortcut on the hand of the service provider, lack of knowledge on the conventional codes that should be used, or for the sake of more flexibility when endpoints change.<p>However, all of those reasons just push more work onto the service consumers. Lack of standardized status codes means the consumer must have customized error detection, which is more susceptible to changes as the provider pushes out updates.