HTTP Status Code Lookup

Building an API's error handling means deciding which status code to actually return for a specific situation, a resource that already exists, 409, a client sending requests too fast, 429, a resource that existed once but is now permanently gone, 410, decisions that go the opposite direction from decoding a code someone else's API already sent back. This tool looks up HTTP status codes by their meaning and typical use case, organized so the right code for a specific situation being built can be found by browsing categories rather than guessing from memory. Useful for choosing the correct status code while designing a new API endpoint's error responses, confirming a less common code like 409 or 429 actually fits the specific situation it's being used for, or browsing the full range of codes in a category before deciding which one an endpoint should return.