# Errors

Mistakes happen, and mostly they will be yours, not ours. Let's look at some status codes and error types you might encounter.

You can tell if your request was successful by checking the status code when receiving an API response. If a response comes back unsuccessful, you can use the error type and error message to figure out what has gone wrong and do some rudimentary debugging (before contacting support).

## Status Codes <a href="#status-codes" id="status-codes"></a>

Here is a list of the different categories of status codes returned by the Underdog API. Use these to understand if a request was successful.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>2xx</strong></td><td>A 2xx status code indicates a successful response.</td><td></td></tr><tr><td><strong>4xx</strong></td><td>A 4xx status code indicates a client error — this means it's a <em>you</em> problem.</td><td></td></tr><tr><td><strong>5xx</strong></td><td>A 5xx status code indicates a server error — you won't be seeing these.</td><td></td></tr></tbody></table>

\ <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.underdogprotocol.com/guides/errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.