AsyncAPI channel · Binance · Binance Spot WebSocket API

/

Single WebSocket connection for sending trading requests and receiving responses. All requests and responses are JSON-formatted messages on this channel. Requests include a method name and parameters; responses include a matching id field.

Open source AsyncAPI → All Binance channels Binance provider profile
Provider: Binance AsyncAPI: v2.6.0 Spec: Binance Spot WebSocket API Operations: 2 Messages: 8

Channel address

/

Operations

publish
receiveResponse
Receive API responses
sendRequest
Send API requests

Messages

orderResponse
Response to an order request.
Content-Type:
accountResponse
Response to an account query.
Content-Type:
marketDataResponse
Response to a market data query.
Content-Type:
errorResponse
Error response for failed requests.
Content-Type:
orderRequest
Request to place a new order via WebSocket.
Content-Type:
cancelOrderRequest
Request to cancel an order via WebSocket.
Content-Type:
accountRequest
Request for account information via WebSocket.
Content-Type:
marketDataRequest
Request for market data via WebSocket.
Content-Type:

About 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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.