ImpervaReese84SensorProxyLess
Generate the raw reese84 sensor payload and post it yourself, so the issued token binds to your own IP.
This is the self-driven reese84 flow. The solver computes the signed sensor payload; you POST it to the reese84 endpoint and read the token out of the response. Because the submission is yours, the resulting cookie is bound to your IP, which is what sites that pin the token to the requesting address require.
Posting the payload
POST /<reese84-script-path>?d=www.example.com HTTP/2
Content-Type: text/plain; charset=utf-8
Accept: application/json; charset=utf-8
User-Agent: <solution.userAgent>
Accept-Language: <solution.acceptLanguage>
<solution.payload>The path is the script path without its query string, with ?d=<hostname> appended. The response is JSON:
{ "token": "3:2wlemniq+CXN97167oNjyw==:EraPjamz…", "renewInSec": 896, "cookieDomain": "www.example.com" }Store token as the reese84 cookie on cookieDomain, then retry the blocked request. Solve again before renewInSec elapses.
Post it exactly as returned
Send the payload as plain text, unmodified, with the userAgent and acceptLanguage from the solution. Imperva
also checks header order, so mirror Chrome's ordering on this request.
Pass reeseUrl when the script cannot be found
If the solver reports that it could not locate the reese84 script, find the POST …?d=<your-domain> in DevTools and
send the full script URL, including its ?s=… query, as reeseUrl. This is also the variant to use when the
target site is unreachable from the solver.
Related tasks
- ImpervaReese84TokenProxyLess: same flow, but the solver posts the payload and hands you the finished cookie.
- ImpervaUtmvcTokenProxyLess: the separate
___utmvcchallenge layer.
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": "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 | 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 |
|---|---|---|---|
payload* | string | Yes | Raw sensor payload. POST it as Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
acceptLanguage | string | No | Accept-Language header the payload was built with. Send the same value when posting it. Example: |
userAgent | string | No | User-Agent string used during solving (if applicable). Example: |