Skip to main content
POST
When you need to step in and interact with a running CDP session in real time, use this endpoint to issue a short-lived control token. Pass the returned controlUrl directly to a WebSocket constructor to begin live control.
string
required
The active CDP session ID you want to take live control of.

Response

boolean
true when the token was issued successfully.
string
A wss:// WebSocket URL with the single-use controlToken already embedded as a query parameter. Pass this directly to new WebSocket(...); do not replace or modify the token.
number
Unix timestamp in milliseconds when the controlToken expires. The token is valid for 30 seconds and can only be used once.
The controlToken expires after 30 seconds and can only be consumed once. If the WebSocket connection fails or is not opened in time, call POST /cdp/live-token again to get a fresh token.

Open the live WebSocket

Open a live-control WebSocket connection to the target session at wss://api.adscrawl.net/cdp/live/{sessionId}?controlToken={token}. The server validates the controlToken, connects to the session backend, and then upgrades your client connection. Once connected, CDP messages are proxied bidirectionally and you have full interactive control.
string
required
The session ID embedded in the controlUrl returned by POST /cdp/live-token.
string
required
The single-use token from POST /cdp/live-token. It must be used within 30 seconds of issuance and can only be consumed once.
When the live-control WebSocket closes, the server sends one of the following reason codes:
Live control tokens are designed for short bursts of manual or conditional interaction. For fully automated workflows, drive the session directly through cdpBaseUrl with Playwright or Puppeteer instead.