# Error

All errors return a consistent envelope with `success: false`.

## Schema

```json
{
  "success": false,
  "error": "Human-readable description of the error"
}
```

## HTTP Status Codes

| Status                      | When                                           |
| --------------------------- | ---------------------------------------------- |
| `400 Bad Request`           | Missing or invalid query parameters            |
| `401 Unauthorized`          | Missing or invalid API key                     |
| `404 Not Found`             | Resource does not exist (e.g. unknown address) |
| `429 Too Many Requests`     | Rate limit exceeded                            |
| `500 Internal Server Error` | Unexpected server-side error                   |

## Examples

```json
// 400
{
  "success": false,
  "error": "Missing required parameter: addr"
}
```

```json
// 401
{
  "success": false,
  "error": "Invalid or missing API key"
}
```

```json
// 429
{
  "success": false,
  "error": "Rate limit exceeded. Try again in 30 seconds."
}
```

## Notes

* Never return a `200` status with `success: false`. Use the appropriate HTTP status code.
* Do not expose internal stack traces or implementation details in the `error` field.


---

# 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.dexpal.io/for-partners/schemas/error.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.