AsyncAPI channel · Tradier · Tradier Streaming WebSocket API

`/v1/markets/events`

Market events streaming channel. After connecting the client sends a JSON subscription payload referencing a sessionid acquired from POST /v1/markets/events/session. The server then streams one or more of the requested payload types (quote, trade, summary, timesale, tradex). The subscription may be modified mid-stream by sending a new payload with the same sessionid.

Open source AsyncAPI → All Tradier channels Tradier provider profile

Provider: Tradier AsyncAPI: v2.6.0 Spec: Tradier Streaming WebSocket API Operations: 2 Messages: 6

Channel address

/v1/markets/events

Operations

publish

subscribeMarketEvents

Send a market data subscription request.

receiveMarketEvents

Receive streamed market data payloads.

Messages

MarketSubscription

Client request to begin or modify a market data stream.

Content-Type: application/json

Quote

Bid/ask quote update for a symbol.

Content-Type: application/json

Trade

Executed trade event for a symbol.

Content-Type: application/json

Summary

Session open, high, low, or previous close update.

Content-Type: application/json

Timesale

Time and sales tick for a symbol.

Content-Type: application/json

Tradex

Extended trade event recommended for pre and post market sessions in place of the trade 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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.