AsyncAPI channel · Tradier · Tradier Streaming WebSocket API

/v1/accounts/events

Account events streaming channel. After connecting the client sends a JSON subscription payload referencing a sessionid from POST /v1/accounts/events/session and the desired event types (currently "order"). The server streams order lifecycle events and periodic heartbeats. Streams may only target either live or sandbox accounts within a session.

Open source AsyncAPI → All Tradier channels Tradier provider profile
Provider: Tradier AsyncAPI: v2.6.0 Spec: Tradier Streaming WebSocket API Operations: 2 Messages: 3

Channel address

/v1/accounts/events

Operations

publish
subscribeAccountEvents
Send an account events subscription request.
receiveAccountEvents
Receive streamed account events.

Messages

AccountSubscription
Client request to begin streaming account events.
Content-Type: application/json
OrderEvent
Order lifecycle event for a streamed account.
Content-Type: application/json
Heartbeat
Stream keep-alive heartbeat.
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.