AsyncAPI channel · Qfex
· QFEX Multiplexed WebSocket API
/v4/ws
Single channel for subscriptions, order commands, and all updates
Channel address
/v4/ws
Operations
receive
subscribePositionsStream
Subscribe to a data stream
receive
subscribeBalanceStream
Subscribe to a data stream
receive
subscribeOrdersStream
Subscribe to a data stream
receive
placeOrder
Place a new order
receive
cancelOrder
Cancel an existing order
send
receiveUpdates
Receive all update messages and events
Messages
subscribe_positions
Subscribe to user positions
Content-Type:
application/jsonsubscribe_balance
Subscribe to user balance
Content-Type:
application/jsonsubscribe_orders
Subscribe to user orders
Content-Type:
application/jsonadd_order
Add order. Ensure you have subscribed to the v4_orders channel first
Content-Type:
application/jsoncancel_order
Cancel order. Ensure you have subscribed to the v4_orders channel first
Content-Type:
application/jsonbbo_update
Best bid and offer updates
Content-Type:
application/jsonorderbook_update
Changes in the L2 order book
Content-Type:
application/jsontrade_update
Public trades
Content-Type:
application/jsoncandle_update
Candle updates over various intervals
Content-Type:
application/jsonbalance_update
User balance updates
Content-Type:
application/jsonposition_update
User position updates
Content-Type:
application/jsonAbout AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.