Home/API Errors

API Errors

This page groups together HTTP and application-style API errors related to request validation, upstream dependencies, and server-side failures.

What 400 Bad Request Means and How to Troubleshoot It
What 405 Method Not Allowed Means and How to Troubleshoot It
What 406 Not Acceptable Means and How to Troubleshoot It
What 411 Length Required Means and How to Troubleshoot It
What 415 Unsupported Media Type Means and How to Troubleshoot It
What 422 Unprocessable Content Means and How to Troubleshoot It
What 500 Internal Server Error in APIs Means and How to Troubleshoot It
What 502 Bad Gateway in APIs Means and How to Troubleshoot It

What this collection covers

How API and request failures are grouped here

This collection focuses on errors that happen when an application, browser, service, or client sends a request that the server, gateway, or upstream system cannot accept or process correctly. That includes malformed requests, bad payloads, unsupported formats, request validation failures, and backend response issues that commonly surface as HTTP errors in APIs and modern web applications.

Use this page when the problem is clearly tied to request/response behavior, structured API calls, payload handling, or service-to-service communication. It works best alongside the more specialized request-validation, payload/upload, and gateway/upstream collections.