> For the complete documentation index, see [llms.txt](https://uliquid-1.gitbook.io/uliquid-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uliquid-1.gitbook.io/uliquid-docs/user-guide/exchange-accounts-and-venue-support.md). # Exchange Accounts and Venue Support Connect exchange accounts safely and verify feature support for the selected venue. An exchange account connects uLiquid Desk to a venue for the features enabled for that account and environment. Support can differ by venue, market type, account configuration, runtime availability, and product rollout. ## Add an Account Safely 1. Open **Settings** and then **Exchange Accounts**. 2. Choose the intended venue and give the account a clear label. 3. Enter only the credentials requested by the form. Some venues require an additional passphrase. 4. Complete re-authentication when prompted. 5. Verify connection status, balances, and read-only data before attempting a live workflow. ## Minimum API-Key Rules * Never enable withdrawal permission for an API key used by uLiquid Desk. * Use only the read and trading permissions required for your intended workflow. * Apply an IP allowlist at the venue when it is available and compatible with your setup. * Keep production, test, and personal accounts clearly separated by label. * Rotate or revoke a key immediately if you suspect exposure; then update the account through the normal secure workflow. ## Verify Venue Capability Before Use Do not infer support from a venue name alone. In the selected account and Trading Desk, confirm that the required action is available for the intended market: * market data and account reads, * spot or perpetual trading, * permitted order type, * leverage or margin-mode control, * position close and protective-order controls, * bot, grid, funding, or vault workflow. The product blocks unsupported combinations. Treat such a block as a compatibility signal, not as something to work around by repeatedly submitting the action. ## Paper and Linked Data Accounts Paper workflows may use linked market data from an eligible account. They are for controlled testing and do not prove that a live venue, credential, order type, or funding workflow is ready for production capital. ## If an Account Is Degraded or Disconnected 1. Stop creating new live actions for that account. 2. Check the venue status, API-key permissions, IP restrictions, and account label. 3. Refresh the account state and compare positions or orders directly with the venue. 4. Do not remove and recreate an account solely to clear an unexplained live-data mismatch. 5. If the problem persists, collect a support package with timestamp, workspace, account label, venue, and displayed error. --- # 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://uliquid-1.gitbook.io/uliquid-docs/user-guide/exchange-accounts-and-venue-support.md?ask=&goal= ``` `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.