AsyncAPI channel · CoinDCX · CoinDCX Streaming Socket.IO API

join

Client-emitted Socket.IO event used to subscribe to a channel. For public market channels the payload is a string such as "B-BTC_USDT@orderbook". For the authenticated user-data channel the payload is a JSON object containing channelName "coindcx", a stringified body with at least a timestamp, an HMAC-SHA256 authSignature of that body computed with the API secret, and the apiKey.

Provider: CoinDCX AsyncAPI: v2.6.0 Spec: CoinDCX Streaming Socket.IO API Operations: 1 Messages: 2

Channel address

join

Operations

publish
joinChannel
Subscribe to a public or authenticated streaming channel.

Messages

PublicJoin
String channel name used to subscribe to a public market channel, for example B-BTC_USDT@orderbook, B-BTC_USDT@trades, B-BTC_USDT@prices, B-BTC_USDT@prices-stats, or candlestick@B-BTC_USDT_1m.
Content-Type: application/json
AuthenticatedJoin
Join payload for the authenticated user-data channel. The body field is a JSON-stringified object containing at least a timestamp; the authSignature is the hex HMAC-SHA256 of that string computed with
Content-Type: application/json

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.