Skip to Content
AnySolver logo
AnySolver
Token

PerimeterXInvisibleToken

Generate PerimeterX sensor data from the init.js script through your proxy and get the PerimeterX cookies, with no challenge page needed.

PerimeterXInvisibleToken runs the PerimeterX flow for a site's init.js through your proxy and returns the PerimeterX cookies. PerimeterX scripts collect browser signals on the page and post them to PerimeterX, which answers with cookies such as _px3. No block page is involved.

If you are looking at a block page with a Press & Hold button, use PerimeterXHoldToken. If you have only the app ID and the provider network is acceptable, use PerimeterXInvisibleTokenProxyLess.

Which PerimeterX task do I need?

What you haveTask
You see a block page with a Press & Hold button, and solve through your proxyPerimeterXHoldToken
You have the init.js URL and the app ID, and solve through your proxyPerimeterXInvisibleToken (this task)
You have only the app ID, and want the provider's invisible task, from the provider networkPerimeterXInvisibleTokenProxyLess
You have only the app ID, and want the provider's standard task, from the provider networkPerimeterXTokenProxyLess

Use your proxy

task.proxy is required on this task type. The provider solves from that address, and the proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve. Replay the cookies from the same IP and with the same User-Agent.

Find the parameters

Open the protected page with DevTools and the Network tab:

FieldWhere to find it
pxAppIdThe app ID: PX followed by letters and digits. It is in the init.js request URL and in window._pxAppId in the console.
perimeterxJsUrlThe full URL of the init.js request. Sites that serve it first-party use a path such as /px/PXxxxxxxxx/init.js on their own domain, where PXxxxxxxxx is the app ID.

Send the protected page as websiteURL.

Use the cookies

Set every cookie in solution.cookies on the session before you request the protected endpoints, and send the returned userAgent when the provider supplies one. If the site rejects the cookies, check that the proxy kept one IP for the whole solve, then that pxAppId and perimeterxJsUrl come from the protected page.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
RiskBypass
$3.00
WTFSolve
$0.20
Solverify
$0.50

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

Per-request settings for routing, Auto Retry, Auto Fallback, proxy reuse, response statistics and detailed analytics. Each field overrides the API key's value. See Routing modes.

View settings reference

Task Object Properties

The task field accepts an object with the following properties:

FieldTypeRequiredDescription
type*
Yes
websiteURL*
URLYes

Full URL of the page where the CAPTCHA is displayed.

Example: https://www.walmart.com/

perimeterxJsUrl*
stringYes

URL of the PerimeterX init.js script the page loads. Sites that serve it first-party use a path such as /px/{pxAppId}/init.js on their own domain.

Example: https://www.walmart.com/px/PXu6b0qd2S/init.js

pxAppId*
stringYes

PerimeterX app ID of the target site: PX followed by letters and digits. Find it in the init.js URL or in window._pxAppId.

Example: PXu6b0qd2S

proxy*
string | objectYes

Proxy the provider solves through, as a string or an object. See Proxy configuration.

View proxy configuration

Example: http://user:pass@1.2.3.4:8080

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "PerimeterXInvisibleToken",
        "websiteURL": "https://www.walmart.com/",
        "perimeterxJsUrl": "https://www.walmart.com/px/PXu6b0qd2S/init.js",
        "pxAppId": "PXu6b0qd2S",
        "proxy": "http://user:pass@1.2.3.4:8080"
    }
}

Optional fields are not guaranteed across providers

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
cookies*
Record<string, unknown>Yes

PerimeterX cookies to set on the session, such as _px3 and _pxvid. Replay them on the target with the same IP and User-Agent.

Example: {"_px3":"a1b2...","_pxvid":"c3d4..."}

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.

userAgent
stringNo

User-Agent string used during solving.

Example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36