> 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-protocol/build-on-flash/flash-trade-v2/guides/stream-live-state.md).

# Stream live state

Subscribe to a wallet's basket over WebSocket.

For live positions and orders, open a WebSocket instead of polling. The server pushes a full snapshot on connect, re-pushes it whenever the basket changes on-chain, and sends lightweight metric ticks in between.

## Connect

```
wss://flashapi.trade/owner/{owner}/ws?updateIntervalMs=1000
```

`updateIntervalMs` sets the metric-tick cadence (default `1000`, min `100`, max `10000`).

## Handle the two message types

```javascript
const ws = new WebSocket(`wss://flashapi.trade/owner/${owner}/ws?updateIntervalMs=1000`);

ws.onmessage = (ev) => {
  const msg = JSON.parse(ev.data);
  if (msg.type === "basket") {
    // Full snapshot: positionMetrics / orderMetrics keyed by market pubkey,
    // plus raw basketData (base64). Sent on connect and on every basket change.
    render(msg.data.positionMetrics, msg.data.orderMetrics);
  } else if (msg.type === "metrics") {
    // Metrics-only tick: positionMetrics keyed by market pubkey. Refresh PnL/liq.
    updateMetrics(msg.data);
  }
};
```

* `basket` — full state; the first message is always a `basket`, so you have bytes before any tick.
* `metrics` — position metrics only, on the oracle-tick cadence, so PnL/leverage/liq keep refreshing cheaply.

The server pings every 30s and closes the socket if no pong arrives within 10s. You don't need to send anything after connecting.

## Limits

Max **5 connections per owner** and **10,000 global** — `429` and `503` respectively.

→ Message protocol and field tables: [API reference › WebSocket](/flash-trade/flash-trade-protocol/build-on-flash/flash-trade-v2/reference/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 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-protocol/build-on-flash/flash-trade-v2/guides/stream-live-state.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.