AsyncAPI channel · Trading Economics · Trading Economics Streaming API (WebSocket)

/

Single WebSocket channel. After connecting, the client publishes one or more subscribe messages naming a market symbol (e.g. EURUSD:CUR) or a named channel (calendar, news, earnings). The server then pushes JSON messages for each subscribed topic over the same connection.

Provider: Trading Economics AsyncAPI: v2.6.0 Spec: Trading Economics Streaming API (WebSocket) Operations: 2 Messages: 3

Channel address

/

Operations

publish
subscribeToTopic
Subscribe to a market symbol or named channel.
receiveStreamMessages
Receive pushed market ticks and release events.

Messages

SubscribeMessage
Client-to-server JSON message subscribing to a topic.
Content-Type:
MarketTick
Server-pushed live quote update for a subscribed market symbol.
Content-Type:
CalendarRelease
Server-pushed event emitted the moment an economic indicator release hits the calendar - for example a central bank interest rate decision or a CPI print.
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 Agent Skill and MCP server surfaces of the same providers.