> For the complete documentation index, see [llms.txt](https://exliquid.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://exliquid.gitbook.io/docs/trading/accounts-and-balances.md).

# Accounts and balances

Exliquid accounts represent the trading identity and collateral state used by orders, positions and risk checks.

## Account identity

A signed trading action identifies the account and signer that authorize it. Integrations should treat account and signing identity as part of the transaction contract rather than as an application-only label.

Where subaccounts are supported, they allow separate trading state under the same owner while preserving explicit account boundaries.

## Balance concepts

User-facing balance views can include values such as:

* total simulated collateral;
* available balance;
* balance reserved by open orders or margin requirements;
* fees and realized PnL effects;
* funding effects;
* isolated-margin allocations where applicable.

Exact response fields are defined by the current API schema.

## Reservations and available balance

Open risk-increasing orders may reduce the amount of collateral available for new actions. As orders fill, cancel or otherwise leave the book, the corresponding reservation can change.

Clients should therefore query fresh account state before making assumptions about how much collateral remains available.

## Balances and fills are connected

A trade is not complete from the account's perspective until its balance, fee and position effects are reflected together.

For trading interfaces and bots, reconcile fills against the updated balance and position state instead of treating a market-data trade message as sufficient account accounting.

## Simulated collateral

The current network line uses simulated collateral. These balances do not represent custody of external assets and are not redeemable unless a future network release explicitly introduces a real-asset system.

## API access

Use:

* `GET /api/v1/accounts/{address}/balances` for balances;
* account WebSocket channels for low-latency updates when authenticated;
* the current SDK for typed account queries where supported.

See [REST API](/docs/developers/rest-api.md) and [WebSocket](/docs/developers/websocket.md).


---

# 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://exliquid.gitbook.io/docs/trading/accounts-and-balances.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.