AsyncAPI channel · Bullish
· Auction Feed
/trading-api/v1/market-data/auction
Channel address
/trading-api/v1/market-data/auction
Operations
send
subscribe
## Subscribe
Multiple subscriptions could be opened within the same websocket.
The auction data of different markets to be subscribed are controlled by the parameters in
the subscription message list
receive
receive-noii
## Receive NOII
receive
receive-phase
## Receive Phase
receive
subscribe-nack
In case of *invalid* subscription message, an error rejection would be sent.
send
keepalive-ping
## Keepalive
In case nothing is subscribed to, keep the websocket connection alive.
receive
keepalive-pong
Acknowledgement returned by the server in response to a keepalive-ping.
Messages
Subscription
Let you subscribe to a given topic
Content-Type:
Acknowledgment
Confirm the topic being subscribed
Content-Type:
NOII Snapshot
Initial NOII state on subscribe
Content-Type:
NOII Update
Net Order Imbalance Indicator update during lockdown or cross result
Content-Type:
Phase Snapshot
Initial auction phase state on subscribe
Content-Type:
Phase Update
Auction phase transition notification
Content-Type:
Rejection
Explain why the topic could not be subscribed
Content-Type:
Keepalive Ping
Keepalive Ping
Content-Type:
Keepalive Pong
Keepalive Pong
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 Agent Skill and MCP server surfaces of the same providers.