AsyncAPI channel · Blockchain.com · Blockchain.com WebSocket APIs

/mercury-gateway/v1/ws#auth

Authenticates the WebSocket connection using an API secret as `token`. As an alternative, a connection may set the `auth_token` cookie header at handshake time, in which case authentication happens automatically without sending this message.

Open source AsyncAPI → All Blockchain.com channels Blockchain.com provider profile
Provider: Blockchain.com AsyncAPI: v2.6.0 Spec: Blockchain.com WebSocket APIs Operations: 2 Messages: 3

Channel address

/mercury-gateway/v1/ws#auth

Operations

publish
subscribeAuth
Submit credentials to authenticate the connection.
receiveAuth
Authentication result.

Messages

ExchangeAuthSubscribe
Authenticate the connection
Content-Type:
ExchangeAuthSubscribed
Authentication accepted
Content-Type:
ExchangeAuthRejected
Authentication failed
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.