AsyncAPI channel · Oddpool
· Oddpool WebSocket Feeds
/ws
The single multiplexed WebSocket connection; messages are addressed by channel string.
Channel address
/ws
Operations
send
authenticate
send
subscribe
receive
receiveDist
Messages
auth
Authenticate the connection with an API key.
Content-Type:
authResponse
Server confirmation with resolved tier and limits.
Content-Type:
subscribe
Subscribe or unsubscribe to channels by event.
Content-Type:
subscribed
Confirms subscribed channels; rejected[] present only on rejections.
Content-Type:
dist
Cross-venue probability distribution for all outcomes of an event.
Content-Type:
book
Normalized orderbook update for one outcome on one venue.
Content-Type:
trade
Trade executions for one outcome.
Content-Type:
snapshot
Full state reset every 60s for all outcomes of an event.
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.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.