# Errors & Status Codes

## Errors Handling

All exceptions encountered during request processing are thoroughly captured and included in the response message, with the status set to `false`. This ensures that errors are communicated clearly and descriptively. In the rare event that an error is not handled as expected, the response message will provide details about the issue, helping you diagnose and address any problems effectively. Below is a default message in case something goes wrong internally.

> Somethiing went wrong internally, If this persist, reachout to our development team.

## Status Codes

Here is a list of our response status codes and their meanings.

| Status Code | Meaning               |
| ----------- | --------------------- |
| 200         | Successful request    |
| 201         | Successfully created  |
| 400         | Bad Request           |
| 401         | Unauthorized          |
| 404         | Content not found     |
| 422         | Request Validation    |
| 500         | Internal Server Error |


---

# 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://developer.goshiip.com/getting-started/errors-and-status-codes.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.