AsyncAPI channel · Alpaca · Alpaca WebSocket Streaming APIs

trade_updates

The trade_updates stream delivers order lifecycle events for a single Alpaca trading account. The client first authenticates with an "auth" action, then subscribes by sending a "listen" action whose data.streams array contains "trade_updates".

Open source AsyncAPI → All Alpaca channels Alpaca provider profile
Provider: Alpaca AsyncAPI: v2.6.0 Spec: Alpaca WebSocket Streaming APIs Operations: 2 Messages: 6

Channel address

trade_updates

Operations

publish
tradingClientSend
Messages the client sends to the trading stream.
tradingServerReceive
Messages the server pushes on the trading stream.

Messages

TradingAuthRequest
Trading stream authenticate
Content-Type:
TradingListenRequest
Subscribes to the trade_updates stream. Sending an empty streams array unsubscribes.
Content-Type:
TradingAuthorizationResponse
Trading auth response
Content-Type:
TradingListeningResponse
Trading listening response
Content-Type:
TradingErrorResponse
Trading error response
Content-Type:
TradeUpdate
Order lifecycle event. The event field carries one of: new, fill, partial_fill, canceled, expired, done_for_day, replaced, rejected, pending_new, stopped, pending_cancel, pending_replace, calculated,
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.

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.