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

/mercury-gateway/v1/ws#heartbeat

Server-pushed heartbeat sent every 5 seconds after subscription.

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#heartbeat

Operations

publish
subscribeHeartbeat
Subscribe / unsubscribe to heartbeats.
receiveHeartbeat
Receive periodic heartbeat updates.

Messages

ExchangeSubscribeAction
Generic subscribe / unsubscribe (no symbol)
Content-Type:
ExchangeAdminEvent
Subscription admin event (subscribed / unsubscribed / rejected)
Content-Type:
ExchangeHeartbeatUpdate
Heartbeat update (every 5 seconds)
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.