ImpervaReese84TokenProxyLess
Get a ready-to-set reese84 cookie for an Imperva / Incapsula protected site from just its URL.
reese84 is Imperva's core bot check: a hidden JavaScript sensor collects device, canvas and timing entropy, and the site only issues a valid reese84 cookie once a correctly signed payload has been posted back. This task runs the whole sequence (locate the script, run it, post the sensor) and returns the finished cookie.
A site uses reese84 when the browser holds a cookie named reese84, or when its requests carry an x-d-token header. If it instead loads /_Incapsula_Resource?SWJIYLWA=…, you are looking at ImpervaUtmvcTokenProxyLess; some sites run both layers.
Using the solution
Set solution.token as the reese84 cookie on the protected domain, then retry the request that was blocked.
Renew instead of re-solving
renewInSec is how long the token stays valid, typically around 15 minutes. Solve again shortly before it elapses
rather than after every request.
Pass reeseUrl when the script cannot be found
The sensor script lives on an obscure, site-specific path. If a task fails because the script could not be located,
find the POST …?d=<your-domain> in DevTools, take its path, and send the full script URL (with its ?s=… query)
as reeseUrl. The path is static per site, so you only look it up once.
The sensor is posted from the solver's IP
This variant submits the payload itself, so the token is minted from Salamoonder's egress rather than yours. On sites that pin the token to the requesting IP, use ImpervaReese84SensorProxyLess and post the payload from the IP you scrape with.
Related tasks
- ImpervaReese84SensorProxyLess: the raw payload, posted by you.
- ImpervaUtmvcTokenProxyLess: the separate
___utmvcchallenge layer. - ImpervaToken: browser-based solve behind your own proxy.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
 | $1.80 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in 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, and proxy behavior. See Routing Strategies. View settings reference |
Task Object Properties
The task field accepts an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
websiteURL* | URL | Yes | Full URL of the Imperva-protected page. The solver loads it to locate and run the challenge script. Example: |
reeseUrl | string | No | Absolute URL of the reese84 script, query string included. Pass it when the solver reports that it could not locate the script itself. Example: |
userAgent | string | No | 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: |
{ "clientKey": "your-api-key-from-dashboard", "task": { "type": "ImpervaReese84TokenProxyLess", "websiteURL": "https://www.pokemoncenter.com/" }}Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes | 0 = success, 1 = external error, 2 = internal error. 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 |
|---|---|---|---|
token* | string | Yes | The Example: |
renewInSec* | number | Yes | Seconds the token stays valid. Solve again before it elapses instead of re-running the whole flow. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent string used during solving (if applicable). Example: |