> For the complete documentation index, see [llms.txt](https://docs.flash.trade/flash-trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flash.trade/flash-trade/flash-trade-v1-deprecated/flash-trade-api/flash-trade-v1/error-handling.md).

# Error Handling

### Error Response Format

All errors return a JSON body with an `error` field:

json

```json
{
  "error": "position account 7xKXtg... not found"
}
```

***

### HTTP Status Codes

| Code  | Meaning             | When                                                                 |
| ----- | ------------------- | -------------------------------------------------------------------- |
| `200` | Success             | Request completed normally                                           |
| `400` | Bad Request         | Invalid pubkey format, invalid parameters, or configuration error    |
| `404` | Not Found           | Account or resource doesn't exist                                    |
| `429` | Too Many Requests   | Per-owner connection limit reached (5 per owner on streaming)        |
| `500` | Internal Error      | Server-side computation error                                        |
| `503` | Service Unavailable | Global connection limit reached (10K) or required price data missing |

***

### Transaction Builder Errors

Transaction builder and preview endpoints return `200` even when computation fails. Always check the `err` field before using response data.

json

```json
{
  "newLeverage": "0",
  "newEntryPrice": "0",
  "err": "Target price not available"
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flash.trade/flash-trade/flash-trade-v1-deprecated/flash-trade-api/flash-trade-v1/error-handling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.