AsyncAPI channel · dYdX
· dYdX v4 Indexer WebSocket API
v4_subaccounts
Streams subaccount state (positions, orders, fills, transfers) for a single address + subaccount number. The subscription `id` is `
/Channel address
v4_subaccounts
Operations
publish
sendSubaccountsSubscription
Send subscribe/unsubscribe envelopes for the subaccounts channel.
subscribe
receiveSubaccounts
Receive subaccount snapshots and incremental updates.
Messages
SubscribeSubaccounts
Subscribe to v4_subaccounts or v4_parent_subaccounts
Content-Type:
UnsubscribeSubaccounts
Unsubscribe from v4_subaccounts or v4_parent_subaccounts
Content-Type:
SubscribedSubaccounts
Initial v4_subaccounts snapshot
Content-Type:
ChannelDataSubaccounts
v4_subaccounts update
Content-Type:
ChannelBatchDataSubaccounts
v4_subaccounts 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.