> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vane.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> How to reach Vane support and what to include so the first reply solves it.

Email [help@vane.xyz](mailto:help@vane.xyz) or open the live chat at [vane.xyz](https://vane.xyz). Chat runs around the clock.

The same address issues tenant API keys. The key in the docs is a shared public key for evaluating the API; request your own before a production integration and keep it server-side.

Include in every report:

* The order UUID. Support can read the full order from it; without it there's nothing to act on.
* The deposit transaction hash from your wallet, or `senderDepositTx` from the order.
* For API issues, the exact request and response, with your key redacted.

Write in when an order shows `ERROR`, when a confirmed deposit hasn't moved the order forward well past its chain's confirmation window, or when you sent funds right at the timeout. Most status questions are answered on [Order lifecycle](/api-reference/order-lifecycle).
