PerimeterXInvisibleTokenProxyLess
Get PerimeterX cookies for a site from its PerimeterX app ID alone, using the provider's invisible task, with no proxy. With the schema, example and prices.
PerimeterXInvisibleTokenProxyLess takes only the PerimeterX app ID of the site and returns PerimeterX cookies. You send no proxy, URL or script. EZ-Captcha maps it to its PxInvisibleCaptcha task, while PerimeterXTokenProxyLess maps to its PerimeterX task.
Which PerimeterX task do I need?
| What you have | Task |
|---|---|
| You see a block page with a Press & Hold button, and solve through your proxy | PerimeterXHoldToken |
You have the init.js URL and the app ID, and solve through your proxy | PerimeterXInvisibleToken |
| You have only the app ID, and want the provider's invisible task, from the provider network | PerimeterXInvisibleTokenProxyLess (this task) |
| You have only the app ID, and want the provider's standard task, from the provider network | PerimeterXTokenProxyLess |
Find pxAppId
The app ID is PX followed by letters and digits. Open the protected page with DevTools: it appears in the init.js request URL (for example /px/PXxxxxxxxx/init.js on first-party setups) and in window._pxAppId in the console.
Use the cookies
Set the cookies in solution.cookies on your session and request the protected endpoints. The solution has no userAgent. Because you send no proxy, the provider uses its own IP. If the site rejects the cookies from your session, use PerimeterXInvisibleToken, which takes your proxy.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
EZCaptcha | $0.50 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in a workspace of the AnySolver dashboard. Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See Tasks for per-task schemas. View task properties |
settings | object | No | 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:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
pxAppId* | string | Yes | PerimeterX app ID of the target site: Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "PerimeterXInvisibleTokenProxyLess",
"pxAppId": "PXu6b0qd2S"
}
}Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes |
Example: | |
taskId | string | No | Unique identifier returned when the task was created. Example: |
errorCode | No | Machine-readable error code. Example: | |
errorDescription | string | No | Human-readable error message with resolution hints. Example: |
cost | number | No | Actual cost charged for this task in USD. Example: |
taskType | No | The type of CAPTCHA task to solve. Example: | |
provider | No | Provider that handled this task. While processing, the provider currently solving it. Example: | |
solution | object | No |
Solution Object Properties
The solution field contains an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
cookies* | Record<string, unknown> | Yes | PerimeterX cookies to set on the session, such as Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |