Skip to Content
AnySolver logo
AnySolver
Other

ImpervaReese84SensorProxyLess

Generate the raw reese84 sensor payload and post it yourself, so Imperva issues the token to your own IP. With the schema, an example and provider prices.

ImpervaReese84SensorProxyLess computes the signed reese84 sensor payload and returns it without posting it. This is the self-driven reese84 flow: you post the payload to the reese84 endpoint and read the token from the response, so Imperva issues the token to your own IP.

Use ImpervaReese84TokenProxyLess if you want the provider to post the payload and return the cookie.

Which Imperva task do I need?

The task depends on the layer and on who makes the requests.

What you needTask
Both layers, and you solve through your own proxyImpervaToken
The reese84 layer, and the provider posts the sensor and returns the cookieImpervaReese84TokenProxyLess
The reese84 layer, and you post the sensor payload yourself from your own IPImpervaReese84SensorProxyLess (this task)
The ___utmvc layer: the HTML loads /_Incapsula_Resource?SWJIYLWA=…ImpervaUtmvcTokenProxyLess

Post the payload

Post the payload as plain text, unmodified, with the solution.userAgent and solution.acceptLanguage of the solution:

POST /<reese84-script-path>?d=www.example.com
Content-Type: text/plain; charset=utf-8
User-Agent: <solution.userAgent>
Accept-Language: <solution.acceptLanguage>

<solution.payload>

The path is the script path from the page, and ?d= carries the hostname of the protected site.

Keep the TLS fingerprint and the header order of a real Chrome on this request. The JSON response has token, renewInSec and cookieDomain.

Set token as the reese84 cookie on cookieDomain, then retry the blocked request. Solve again before renewInSec elapses.

Optional parameters

  • reeseUrl: set it when the provider reports that it could not locate the reese84 script. Find the POST request that ends with ?d=<your-domain> in DevTools and pass its script URL, with the ?s=… query. Set it as well when the provider cannot reach the target site.
  • userAgent: the User-Agent to use for the solve.

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

Supported Providers

ProviderPrice per 1,000Routing
Salamoonder
$1.80

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 Imperva-protected page. The provider loads it to locate and run the challenge script.

Example: https://www.pokemoncenter.com/

reeseUrl
stringNo

Absolute URL of the reese84 script, query string included (for example ?s=…). Pass it when the provider reports that it could not locate the script itself.

Example: https://www.pokemoncenter.com/vice-come-Solden...

userAgent
stringNo

Browser User-Agent string. Must match the browser used on the target page. Not all providers properly support this parameter. Verify the compatibility with the provider you are using.

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

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "ImpervaReese84SensorProxyLess",
        "websiteURL": "https://www.pokemoncenter.com/"
    }
}

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
payload*
stringYes

Raw sensor payload. POST it unmodified as text/plain; charset=utf-8 to the reese84 script path with ?d=<domain> appended.

Example: {"solution":{"interrogation":{"p":"V33Hw0cqFIs8LgTT...

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.

acceptLanguage
stringNo

Accept-Language value the payload was built with. Send the same value when posting it.

Example: en-US,en;q=0.9

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