Skip to main content

Guides

AdsPower-compatible Local API

Run existing AdsPower Local API scripts against Browlix on the same machine, with a Browlix API key on every call.

View as Markdown

If you have scripts written for the AdsPower Local API, a machine running the Browlix worker can answer a subset of it locally. Every call is translated into Browlix API v1 operations made with your own Browlix API key, so permissions, limits, audit and idempotency are exactly those of the public API.

Turn it on

In the web app open the machine and enable the AdsPower-compatible API, or call devices.adspower_api.set with enabled: true and optionally port (default 50325, AdsPower's own default).

Supported calls (manifest adspower-8.9.23)

CallNotes
GET /statusLiveness
GET /api/v1/browser/start, POST /api/v2/browser-profile/startAnswers success only once the Browlix session is ready
GET /api/v1/browser/stop, POST /api/v2/browser-profile/stopWaits for the session to close
GET /api/v1/browser/active, GET /api/v1/browser/local-active, GET /api/v2/browser-profile/activeOpen sessions
GET /api/v1/user/list, POST /api/v2/browser-profile/listProfiles visible to the key
GET /api/v1/group/listProfile groups

Anything else — creating, updating or deleting profiles, cookies, proxies, tags, sharing — answers "unsupported"; use the Browlix API for those.

Differences from AdsPower

  • Listens on 127.0.0.1 only, refuses foreign Host headers and requests sent by web pages.
  • A Browlix API key is required on every /api/* call (Authorization: Bearer bxk_…), including the cases where AdsPower would skip it.
  • ws.puppeteer is a URL on this listener that relays to the session's ticket-checked broker. No DevTools port is ever opened, so ws.selenium, debug_port and webdriver are always empty.
  • Profile ids are Browlix ids.