AsyncAPI channel · River Markets
· River Markets Streaming API
/v1/ws/tradeprints
Live trade tape (every print) for one or more markets (subscribe by river_ids).
Channel address
/v1/ws/tradeprints
Operations
receive
receiveTradeprints
Messages
subscribeRiverIds
Content-Type:
serverEvent
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.