Browser API

Browser API SDK Strategy

Use small wrappers around discovery and CDP rather than hiding runtime target identity. JavaScript and Python examples should rediscover targets after reconnects.

Generated helpers

Download thin discovery SDKs

The helpers are generated from the Browser API contract and intentionally stay small: they discover the running browser, list targets, resolve the current target and return its CDP WebSocket URL. They do not hide runtime target identity.

JavaScript / Node.js

Zero external runtime dependencies on modern Node.js with built-in fetch.

Download JavaScript helper →

Python

Standard-library discovery helper using urllib. Add your preferred CDP/WebSocket library for protocol control.

Download Python helper →

const { SocialBrowserAPI } = require('./social-browser-api.js'); const api = new SocialBrowserAPI('http://127.0.0.1:60101'); const target = await api.resolveTarget({ type: 'page' }); console.log(target.webSocketDebuggerUrl);

Machine-readable contract SDK README

Identity

Runtime IDs are not stable resource IDs

Rediscover targetId, webContentsId and current WebSocket targets after restart or reconnect. Persist your own stable Profile/workflow identity instead.

Browser API overview

Choose the right integration path.

Overview →

External/CDP setup

Set up the API/CDP client and discovery flow.

Setup →

Examples

Use practical examples and target-selection patterns.

Examples →