Base URL
/v2.
Authentication
Pass your Client API key inX-Api-Key.
Dates and Usage Periods
Usage endpoints return UTC rollups:
Date filters use RFC 3339 date or datetime strings.
Errors
v2 errors use a JSON object withcode, message, and details.
unauthorized, forbidden, invalid_request, insufficient_balance, account_not_configured, not_found, upstream_error, and internal_error.
Cloud Browser operations can also return settings_in_use, settings_limit_reached, session_not_active, and connection_in_use. When present, use details.target, details.recoveryHint, details.activeSessionId, and details.nextOperationId to decide what to fix or call next. Include details.requestId when contacting support about an upstream or internal failure.
Cloud Browser WebSocket Connections
Create or get an active browser session, then pass its signedconnectUrl directly to Playwright or Puppeteer. The WebSocket relay does not use the X-Api-Key header and permits one active connection per session.
If the connection token is invalid or expired, get the active session again for a fresh connectUrl. If keepAlive is true, a disconnected session can reconnect until expiresAt; otherwise closing the relay stops the session.
OpenAPI
The current v2 OpenAPI source is available at:api-reference/openapi.jsonfor v2api-reference/openapi-v1.jsonfor legacy v1