AdsPower SOP

Appearance

Test ​

Classification: NEEDS-DESKTOP ​

Status: NEEDS-DESKTOP AdsPower is a Windows and Mac desktop antidetect browser with built-in RPA automation. It cannot be run headlessly or installed via a package manager alone. The desktop app must be downloaded and running for the Local API to be reachable. A free plan is available (limited to 2 profiles).

Install method: Download the installer from adspower.com and run it. Create an account and log in inside the app before using the API or CLI.

Cost/access: Free plan available (2 profiles). Paid plans for more profiles and team features.

Smoke Test 1: CLI Version Check ​

After npm install -g adspower-browser, confirm the package installed and the binary resolves:

bash
ads --version

Expected success output:

1.x.x

Any semantic version string printed to stdout without error confirms a working install.

Smoke Test 2: CLI Status Check ​

With ADS_API_KEY set and the AdsPower desktop client running:

bash
ads status

Expected success output:

json
{
  "code": 0,
  "msg": "success",
  "data": {
    "status": "active"
  }
}

A "code": 0 response confirms the CLI can reach the Local API and the runtime is up.

Smoke Test 3: Local API Health Check (curl) ​

With the AdsPower desktop client running on the default port:

bash
curl "http://localhost:50325/status"

Expected success output:

json
{"code":0,"msg":"success"}

If the port is unreachable, AdsPower is not running or uses a different port. Check the AdsPower client settings under Settings > API for the configured port number.

Smoke Test 4: List Browser Profiles via CLI ​

bash
ads get-browser-list '{}'

Expected success output (example with one profile):

json
{
  "code": 0,
  "msg": "success",
  "data": {
    "list": [
      {
        "user_id": "abc123",
        "name": "Profile 1",
        "group_id": "0",
        "domain_name": "",
        "username": "",
        "remark": ""
      }
    ],
    "page": 1,
    "page_size": 10
  }
}

An empty list ("list": []) is also a passing result if no profiles have been created yet; the important check is "code": 0.

Notes ​

  • Tests 2 through 4 require the AdsPower desktop client to be running and a valid API key configured.
  • The CLI smoke test (Test 1) can be run immediately after npm install -g adspower-browser with no account needed.
  • The desktop client is a GUI application and cannot be installed or tested in a headless CI environment without the full binary.