Guides

Local API: starting profiles from Playwright

An API key, starting a profile on 127.0.0.1 and connecting Playwright over CDP or Juggler. With code samples.

inoBrowser Team3 min read
Contents
  1. Issue a key
  2. Check that the API responds
  3. Start a profile
  4. Connect Playwright
  5. Stop the profile
  6. Limits and security

The client’s local API starts and stops profiles from your scripts. A profile launches with its own fingerprint, proxy and cookies, and you get back an endpoint to connect Playwright or Puppeteer. The full list of methods is in the API docs.

Issue a key

A member issues keys in Settings → API. Each key has permissions, categories, an expiry date and an IP allowlist. The key is shown once and stored as a hash, and it never has more rights than its owner.

Check that the API responds

The API only runs locally, on 127.0.0.1. The default port is 50380; you can change it in settings.

Terminal
curl http://127.0.0.1:50380/health

Start a profile

Send POST /v1/profiles/{id}/start with the key in the Authorization header. The response contains protocol and wsEndpoint: cdp for Chromium, juggler for Firefox, adb for Android.

Terminal
curl -X POST \  -H "Authorization: Bearer $INO_API_KEY" \  http://127.0.0.1:50380/v1/profiles/$ID/start

Connect Playwright

A Chromium profile connects via chromium.connectOverCDP, a Firefox profile via firefox.connect. The browser’s first context is the profile’s context, with its cookies and tabs.

Node.js
import { firefox, chromium } from 'playwright'; const api = 'http://127.0.0.1:50380';const headers = { Authorization: 'Bearer ' + process.env.INO_API_KEY };const id = process.env.PROFILE_ID; const res = await fetch(api + `/v1/profiles/${id}/start`, {  method: 'POST', headers,});const { protocol, wsEndpoint } = await res.json();const browser = protocol === 'cdp'  ? await chromium.connectOverCDP(wsEndpoint)  : await firefox.connect(wsEndpoint); const context = browser.contexts()[0];const page = await context.newPage();await page.goto('https://pixelscan.net');

Puppeteer connects to Chromium profiles the same way — puppeteer.connect({ browserWSEndpoint: wsEndpoint }).

Stop the profile

When the script is done, call POST /v1/profiles/{id}/stop. Changes to the profile folder upload to the server and the profile is free for your teammates.

Limits and security

  • Up to 5 concurrent API launches by default; the limit is configurable.
  • Every call is written to the log.
  • Reissuing a key keeps the old one working for 24 hours; revoking takes effect immediately.
  • Our Chromium is automated without CDP traces: an isolated world without Runtime.enable, launched without the Playwright flags that disable storage partitioning.

Read next

All articles

Try it free with 3 profiles

© 2026 inoBrowserinobrowser.run