AsyncAPI channel · Coinbase Pro · Coinbase WebSocket APIs

`exchange/full`

Authenticated stream of every order lifecycle event required to maintain a Level 3 order book: `received`, `open`, `done`, `match`, `change`, `activate`.

Open source AsyncAPI → All Coinbase Pro channels Coinbase Pro provider profile

Provider: Coinbase Pro AsyncAPI: v2.6.0 Spec: Coinbase WebSocket APIs Operations: 2 Messages: 7

Channel address

exchange/full

Operations

publish

exchangeFullSubscribeRequest

exchangeFullSubscribe

Messages

ExchangeSubscribeAuthenticated

Subscribe envelope required for the `full` and `user` channels. Adds `signature`, `key`, `passphrase`, `timestamp`.

Content-Type: application/json

ExchangeFullReceived

Exchange full - received

Content-Type: application/json

ExchangeFullOpen

Exchange full - open

Content-Type: application/json

ExchangeFullDone

Exchange full - done

Content-Type: application/json

ExchangeFullMatch

Exchange full - match

Content-Type: application/json

ExchangeFullChange

Exchange full - change

Content-Type: application/json

ExchangeFullActivate

Exchange full - activate

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.