AsyncAPI channel · Polygon.io · Polygon.io WebSocket APIs

control

Control channel for client-to-server messages. After the connection is established, the client must send an `auth` message with its API key, then issue `subscribe` and `unsubscribe` messages whose `params` field is a comma-separated list of `.` tuples (e.g. `T.AAPL,T.MSFT`, `Q.*`, `AM.O:A230616C00070000`). The server acknowledges each control message with a `status` event.

Open source AsyncAPI → All Polygon.io channels Polygon.io provider profile
Provider: Polygon.io AsyncAPI: v2.6.0 Spec: Polygon.io WebSocket APIs Operations: 2 Messages: 4

Channel address

control

Operations

publish
sendControlMessage
Send auth, subscribe, or unsubscribe control messages.
receiveStatusMessage
Receive connection / auth / subscription status events.

Messages

AuthMessage
Authenticate the WebSocket session with an API key.
Content-Type: application/json
SubscribeMessage
Subscribe to one or more topics.
Content-Type: application/json
UnsubscribeMessage
Unsubscribe from one or more topics.
Content-Type: application/json
StatusMessage
Server-side status update for connect, auth, subscribe, and unsubscribe operations.
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.