> For the complete documentation index, see [llms.txt](https://docs.wheelx.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wheelx.fi/api-and-developer/getting-started/troubleshooting.md).

# Troubleshooting

Common issues and solutions for WheelX API integration.

### HTTP Error Codes

| Code | Meaning      | Solution                                          |
| ---- | ------------ | ------------------------------------------------- |
| 400  | Bad Request  | Check request body format and required parameters |
| 404  | Not Found    | Verify order ID or endpoint path                  |
| 429  | Rate Limited | Implement exponential backoff                     |
| 500  | Server Error | Retry with backoff; contact support if persistent |

### Common Scenarios

#### Quote Returns Empty

* Verify chain IDs and token addresses are correct
* Check that the token pair is supported
* Try a smaller amount if liquidity is insufficient

#### Order Stuck in Processing

* Cross-chain transactions may take several minutes
* Check the source chain block explorer
* Contact support if pending > 30 minutes

#### Webhook Not Firing

* Verify webhook URL is accessible
* Check webhook secret configuration
* Ensure events are properly subscribed


---

# 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 dynamically by asking a question.

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

```
GET https://docs.wheelx.fi/api-and-developer/getting-started/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.