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 EconomicsAsyncAPI: v2.6.0Spec: Trading Economics Streaming API (WebSocket)Operations: 2Messages: 3
Channel address
/
Operations
publish
subscribeToTopic
Subscribe to a market symbol or named channel.
subscribe
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.