ImpervaReese84TokenProxyLess
Get a ready-to-set reese84 cookie for an Imperva (Incapsula) protected site from its URL. Shows the request schema, an example and provider prices.
ImpervaReese84TokenProxyLess solves Imperva's reese84 check from the site URL and returns the finished reese84 token. reese84 is Imperva's core bot check: a hidden JavaScript sensor collects device, canvas and timing data, and the site issues a valid reese84 token only after a correctly signed payload is posted back to the sensor endpoint. This task locates the script, builds the payload, posts it and returns the token.
A site uses reese84 when the browser holds a cookie named reese84, or when its requests carry an x-d-token header. If the page loads /_Incapsula_Resource?SWJIYLWA=… instead, it uses ImpervaUtmvcTokenProxyLess. Some sites run both layers. A site that shows a "Pardon Our Interruption" page runs the dynamic variant of reese84, which adds a proof-of-work step.
Which Imperva task do I need?
The task depends on the layer and on who makes the requests.
| What you need | Task |
|---|---|
| Both layers, and you solve through your own proxy | ImpervaToken |
| The reese84 layer, and the provider posts the sensor and returns the cookie | ImpervaReese84TokenProxyLess (this task) |
| The reese84 layer, and you post the sensor payload yourself from your own IP | ImpervaReese84SensorProxyLess |
The ___utmvc layer: the HTML loads /_Incapsula_Resource?SWJIYLWA=… | ImpervaUtmvcTokenProxyLess |
Optional parameters
reeseUrl: the sensor script is served from a path that is specific to the site. If the task fails because the script could not be located, find thePOSTrequest that ends with?d=<your-domain>in DevTools. Its path is the script path. Pass the full script URL, including its?s=…query, asreeseUrl. The path stays the same for a site, so you look it up once.userAgent: the User-Agent to use for the solve.
Use the token
Set solution.token as the reese84 cookie on the protected domain, then retry the request that was blocked. Send the returned solution.userAgent with it.
solution.renewInSec is the number of seconds the token stays valid. Solve again before it elapses, instead of repeating the whole flow after every request.
This variant posts the payload from the provider's network, so Imperva issues the token to that network instead of yours. If the site ties the token to the requesting IP, use ImpervaReese84SensorProxyLess and post the payload from the IP you send your requests from.
Related tasks
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
Salamoonder | $1.80 |
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 | ||
websiteURL* | URL | Yes | Full URL of the Imperva-protected page. The provider loads it to locate and run the challenge script. Example: |
reeseUrl | string | No | Absolute URL of the reese84 script, query string included (for example 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",
"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 |
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. Example: |