A STORY ABOUT HTTP STATUS CODES AND WHY YOU SHOULD READ DOCUMENTATION

Summary from the TLDR Web Dev newsletter

This article discusses the importance of understanding HTTP status codes and reading API documentation. The author encountered an error triggered by a typo in a Twitch API call. Surprisingly, the API returned an HTTP 200 status code (indicating success) for a non-existent user, which should logically have resulted in a 404 (not found) error. This incident highlighted the need for correct HTTP status codes in API responses and the importance of defensive coding.