AdsPower compatibility

Use the optional compatibility listener only for integrations built for its supported contract. Changing a native API port alone does not convert an integration.

Separate contracts

Property	Native	Compatibility
Default listener	127.0.0.1:47300	127.0.0.1:50325 (disabled by default)
Start route	POST /api/v1/profiles/{id}/start	GET /api/v1/browser/start?user_id=…
Alternative start	Use native schema	POST /api/v2/browser-profile/start
Success check	HTTP status plus result	code === 0
Failures	HTTP status and error.code	Often HTTP 200 with code: -1 and msg

Configure explicitly

Enable and inspect AdsPower compatibility in the app settings. It has its own port and token requirement; the default requires a token. Keep authentication enabled and use the intended scoped credential. A configured legacy key uses the scripts scope preset and does not permit reading secrets. Do not assume the native /openapi.json covers compatibility routes.

Supported runtime examples

Compatibility listener only

GET /api/v1/browser/active?user_id=PROFILE_ID
GET /api/v1/browser/start?user_id=PROFILE_ID
GET /api/v1/browser/stop?user_id=PROFILE_ID
POST /api/v2/browser-profile/start
{"profile_id":"PROFILE_ID"}

V1 accepts user_id or serial_number; V2 uses profile_id or profile_no. Start data contains ws.selenium, ws.puppeteer, debug_port and webdriver; webdriver can be empty when no matching executable is configured or found. Browser state and installed engines remain TabGecko’s, not the other product’s.

Compatibility is not identity

Only implemented routes and mappings are supported. Inspect msg for ignored fingerprint fields or fields stored without runtime effect. A code: 0 response does not prove every imported setting took effect. No claim of complete vendor API parity, identical fingerprints or third-party plan access is made.