API REFERENCE

Automation API

Launch a fingerprinted Chromium or Firefox from Selenium · Playwright · Puppeteer in 5 minutes. Burst (one-off identity), saved profiles, browser engine selection — all in one API.

₩5 per call · 300 calls/day = ₩1,500. Issue your API key and top up points from My Page.

₩5
per call
₩1,500
300 calls/day
₩45,000
9,000 calls/month

Table of contents

1. Prerequisites

  • Desktop app v0.1.23 or later running, activated with a license key (device-bound)
  • API calls go to the same PC at http://127.0.0.1:9333 (Local API). 127.0.0.1 only — LAN blocked
  • X-API-Key header with your SDK API key (sk_…) — see the "SDK API Key" section on the Web My Page
  • If any one family member (main + sub) is activated, the shared API key works

2. Auth & key model

Two key types — don't confuse them:

KeyExample formatPurpose
App login keyADP-XXXX-XXXX-XXXX-XXXXDesktop app activation. Main and sub get separate keys
SDK API keysk_xxxxxxxx_yyyyFor every API call in this doc. One main key shared across the family

Common headers

X-API-Key: sk_xxxxxxxx_yyyy
Content-Type: application/json

3. Sub-account family sharing

  • One SDK API key per family (main) — the whole family (main + subs) shares it (subs have no separate sk_)
  • Shared profile pool — subs see and run the main account's profiles
  • Quota (maxProfiles) = main's plan. Combined main + subs can't exceed the cap
  • Active device: even if the main is unbound, the API works as long as at least one sub is active
  • Sub device unbind: /account → sub table → [Unbind device]
Checking…