FINGER TRADER

marketDataDocsPage.wsDepth

WebSocket Market Depth

Subscribe to bid/ask depth updates on the authenticated market-data socket. Depth support and returned levels depend on the broker and market configuration.

Documentation framework · Overview

Subscribe to depth updates: action 3, msgType 3. Incoming depth messages use msgType 2.

The Flutter app uses the configured Finger Trader market socket. Obtain a WebSocket ticket with the authenticated ticket endpoint, then connect using that ticket. Do not reuse or publish tickets; they are session credentials.

POST /ws-api/v1/auth/build-ticket on the Finger Trader socket service with the account Bearer token. The app sends JSON and reads the ticket from the standard API response data field.

{"action":3,"fromUserId":"<SESSION_USER_ID>","timestamp":"<EPOCH_MILLISECONDS>","msgType":3,"msgId":"<UNIQUE_MESSAGE_ID>","content":{"tickerList":["<TICKER>"]}}

Quote messages include marketType, ticker, time, change, percent, volume, number, high, low, ask, bid, open, close, and quoteVolume. Depth messages include marketType, ticker, time, ask levels, and bid levels. Delivery cadence and depth size are not specified by the client contract.

2. Connect to the production socket · Subscribe to depth updates: action 3, msgType 3. Incoming depth messages use msgType 2.

POST /ws-api/v1/auth/build-ticket on the Finger Trader socket service with the account Bearer token. The app sends JSON and reads the ticket from the standard API response data field.

Ready. Nothing is sent until you select Send request.

The response will appear here.

The Access Token stays in this page memory and is not saved to browser storage or sent to Finger Trader website servers. It is sent only to the selected official API environment after you click Send request. Clear it when finished.

These are the marketType enum values defined by the Flutter client, not a list of markets enabled for your broker. Your broker determines availability from its account and connectivity setup, so ask it for the supported-market list. Use the matching code in REST market filters and history requests. For WebSocket subscriptions, first find the broker-configured ticker in that market, then subscribe to the ticker. A ticker-list query can help inspect returned instruments, but an empty result alone does not prove the market is unsupported.