AsyncAPI channel · Refinitiv
· Refinitiv Real-Time WebSocket API
ping
Heartbeat channel for keeping the WebSocket connection alive. The server sends periodic ping messages and the client must respond with pong messages to maintain the connection.
Channel address
ping
Operations
publish
sendPong
Send pong heartbeat response
subscribe
receivePing
Receive ping heartbeat
Messages
PongMessage
Client heartbeat response to a server ping message.
Content-Type:
PingMessage
Server heartbeat message that must be responded to with a pong.
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.