AsyncAPI channel · Bright Data · Bright Data Scraping Browser (Browser API) - CDP over WebSocket

/

The single CDP WebSocket channel. After the socket is established, the client and server exchange Chrome DevTools Protocol JSON-RPC messages. The client publishes CDP command envelopes; the server publishes CDP command results and asynchronous CDP events (including Bright Data custom events such as `Captcha.solveFinished`).

Provider: Bright Data AsyncAPI: v2.6.0 Spec: Bright Data Scraping Browser (Browser API) - CDP over WebSocket Operations: 2 Messages: 3

Channel address

/

Operations

publish
sendCdpCommand
Send a CDP command (client to browser).
receiveCdpMessage
Receive a CDP result or event (browser to client).

Messages

CdpCommand
A Chrome DevTools Protocol command sent by the client.
Content-Type: application/json
CdpResult
A result returned by the browser for a prior command id.
Content-Type: application/json
CdpEvent
An asynchronous event emitted by the browser.
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 Agent Skill and MCP server surfaces of the same providers.