All articles

Migration

Moving to OwlXBrowser from another antidetect browser takes two steps: bring your accounts, then point your scripts at OwlX.

1. Bring your accounts

Export your profiles from the other app as a spreadsheet (CSV), then use Profiles → Import in OwlX. One row becomes one profile: name, notes, tags, group, proxy, the site and its login, password, 2FA secret and cookies. Columns may be in any order and common column names are recognised. You see a preview with every problem row before anything is created. Every imported profile gets a new fingerprint from OwlX. See Batch create and import for the full column list.

2. Keep your automation scripts

The Local API has its own endpoints under /v1/. Many automation scripts are written for one of two widely used local-API styles; the Local API also answers the request paths of both styles below, with the same response shape, so such scripts run against OwlX profiles after two changes:

  • the address: http://127.0.0.1:50380 (or set OwlX's Local API port to the one your script uses), and
  • your OwlX API key in the Authorization: Bearer header. OwlX never accepts requests without a key, so websites and other people on your network can't drive your browser.

Style 1 — /api/v1/browser/… and /api/v1/user/… paths

RequestWhat it does
GET /statusCheck the API is up
GET /api/v1/browser/start?user_id= or ?serial_number=Start a profile; answers data.ws.puppeteer, data.ws.selenium, data.debug_port. launch_args (JSON array) adds switches for this start
GET /api/v1/browser/stop, /browser/active, /browser/local-activeStop, status, open profiles
GET /api/v1/user/listProfiles (page, page_size up to 100, group_id, user_id, serial_number)
POST /api/v1/user/createCreate: name, group_id, remark, domain_name, username, password, fakey, cookie, user_proxy_config
POST /api/v1/user/update, /user/delete, /user/regroupChange, move to the trash, move to a group
GET /api/v1/group/list, POST /api/v1/group/createGroups

Answers use code: 0 for success, or code: -1 with msg.

Style 2 — /v1.0/browser_profiles/… paths

RequestWhat it does
GET /v1.0/browser_profiles/{id}/start?automation=1Start; answers automation.port and automation.wsEndpoint
GET /v1.0/browser_profiles/{id}/stopStop

user_id / {id} is the OwlX profile id or its number (the "No." column). Fingerprints are always OwlX's own; fingerprint settings sent by a script are ignored. These endpoints drive Chrome profiles (Firefox profiles use /v1/profiles/{id}/start).

OwlXBrowser is an independent product and is not affiliated with, endorsed by or sponsored by any other antidetect browser.