AsyncAPI channel · dYdX
· dYdX v4 Indexer WebSocket API
v4_trades
Streams executed trades for a single perpetual market. The `id` of the subscription is the market ticker (e.g. `BTC-USD`).
Channel address
v4_trades
Operations
publish
sendTradesSubscription
Send subscribe/unsubscribe envelopes for the trades channel.
subscribe
receiveTrades
Receive trade snapshots and incremental fills.
Messages
SubscribeMarketScoped
Subscribe to a single market (trades or orderbook)
Content-Type:
UnsubscribeMarketScoped
Unsubscribe from a single market (trades or orderbook)
Content-Type:
SubscribedTrades
Initial v4_trades snapshot
Content-Type:
ChannelDataTrades
v4_trades update
Content-Type:
ChannelBatchDataTrades
v4_trades batched updates
Content-Type:
Unsubscribed
Unsubscribed acknowledgement
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.