AsyncAPI channel · Finnhub
· Finnhub WebSocket API
/
The single Finnhub WebSocket endpoint. Clients send subscribe / unsubscribe envelopes to select streams; the server pushes trade, news, and press-release messages on the same channel, distinguished by the top-level `type` field.
Receive trade, news, and press-release stream messages.
Messages
subscribeTrade
Subscribe to real-time trades / last-price updates for a US stock, LSE symbol, forex pair, or crypto pair.
Content-Type: application/json
unsubscribeTrade
Unsubscribe from real-time trades for a symbol.
Content-Type: application/json
subscribeNews
Subscribe to real-time news for a US or Canadian stock. Requires Premium access.
Content-Type: application/json
unsubscribeNews
Unsubscribe from real-time news for a symbol.
Content-Type: application/json
subscribePressRelease
Subscribe to real-time press releases for a company. Requires Enterprise access.
Content-Type: application/json
unsubscribePressRelease
Unsubscribe from real-time press releases for a symbol.
Content-Type: application/json
tradeMessage
Real-time trade / last-price update message. `data` may contain multiple trades. For exchanges that do not stream trades, a price update is sent with `v = 0`.
Content-Type: application/json
newsMessage
Real-time news message for subscribed US/Canadian stocks.
Content-Type: application/json
pressReleaseMessage
Real-time press release message for subscribed companies.
Content-Type: application/json
pingMessage
Heartbeat ping sent by the server to keep idle connections alive. Carries no `data` payload.
Content-Type: application/json
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.