Skip to main content

General WSS information

Base Address​

production environment: wss://f-ws.azverse.net/ws/account/futures

production environment: wss://f-ws.azverse.xyz/ws/account/futures

sandbox environment: wss://f-ws.az-qa2.xyz/ws/account/futures

Request Headers​

The request header of the compression extension protocol must be added.

Sec-Websocket-Extensions:permessage-deflate

Protocol​

  • Authentication is at handshake time (fail-closed). Carry a valid, unexpired login token on the WebSocket upgrade request in any one of: query string (?token=<token> or ?zToken=<token>), cookie (token / zToken), or Authorization: Bearer <token> header. If the token is missing / invalid / expired, the server rejects the handshake with HTTP 401 and closes the connection (there is no in-band error frame).

  • Subscribe with plain channel names (no @listenKey suffix): {"method":"SUBSCRIBE","params":["order"],"id":"test1"}; the ack is {"id":"test1","code":200,"msg":"success"}.

  • Push frames are flat and carry a ch field (the channel name), the payload data, and a server millisecond timestamp ts: {"ch":"order","data":{...},"ts":1731231231000}.

  • Heartbeat is the plain text ping -> pong; the connection is disconnected after 60s reader idle.

  • User-related data is pushed after a successful subscription.