AsyncAPI channel · Coinbase Pro
· Coinbase WebSocket APIs
exchange/user
Authenticated, user-filtered variant of `full`. Only includes messages relevant to the API key that signed the subscription.
Channel address
exchange/user
Operations
publish
exchangeUserSubscribeRequest
subscribe
exchangeUserSubscribe
Messages
ExchangeSubscribeAuthenticated
Subscribe envelope required for the `full` and `user` channels.
Adds `signature`, `key`, `passphrase`, `timestamp`.
Content-Type:
application/jsonExchangeFullReceived
Exchange full - received
Content-Type:
application/jsonExchangeFullOpen
Exchange full - open
Content-Type:
application/jsonExchangeFullDone
Exchange full - done
Content-Type:
application/jsonExchangeFullMatch
Exchange full - match
Content-Type:
application/jsonExchangeFullChange
Exchange full - change
Content-Type:
application/jsonExchangeFullActivate
Exchange full - activate
Content-Type:
application/jsonAbout 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.