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 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 |
| The reese84 layer, and you post the sensor payload yourself from your own IP | ImpervaReese84SensorProxyLess (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 thePOSTrequest 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.
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": "ImpervaReese84SensorProxyLess",
"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 |
|---|---|---|---|
payload* | string | Yes | Raw sensor payload. POST it unmodified as Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
acceptLanguage | string | No |
Example: |
userAgent | string | No | User-Agent string used during solving. Example: |