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.

Open source AsyncAPI → All Finnhub channels Finnhub provider profile

Provider: Finnhub AsyncAPI: v2.6.0 Spec: Finnhub WebSocket API Operations: 2 Messages: 10

Channel address

/

Operations

publish

sendControlMessage

Send subscribe / unsubscribe control messages.

receiveStreamMessage

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.

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.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this

find_channelsBrowse and filter every channel in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This channel

curl "https://apis.io/api/v1/channels/untitled"

All event channels

curl "https://apis.io/api/v1/channels?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.