ImpervaToken

Solve an Imperva / Incapsula block through your own proxy and get back the full cookie jar to replay.

Imperva (formerly Incapsula) fronts enterprise login, checkout and API endpoints. ImpervaToken is the managed variant: the solver loads the challenge script through the proxy you supply and returns the cookie jar that clears the block.

Collecting the inputs

Request the protected page through the proxy you will pass to the task, and keep the blocked response. It carries the incap_ses_* and visid_incap_* cookies you send as incapsulaCookies.

Read the challenge script URL out of that response: the src matching /_Incapsula_Resource?SWJIYLWA=…, and send its absolute form as incapsulaScriptUrl. It rotates, so read it fresh on every block.

If the site also guards the page with reese84, add reese84UrlEndpoint: the path the page POSTs its sensor to, visible in DevTools as POST …?d=<your-domain>.

Replay every cookie from solution.cookies on the request that was blocked, over the same proxy.

One IP, one User-Agent, start to finish

The cookies are bound to the proxy exit IP and the User-Agent used during solving. Use a sticky proxy and the same UA for triggering the block, solving, and replaying, and match your TLS fingerprint and header order to a real browser, since correct cookies on a mismatched client are still refused.

Proxyless alternatives

If you would rather keep the HTTP yourself, the challenge splits into two request-based tasks:

ImpervaReese84TokenProxyLess / ImpervaReese84SensorProxyLess: the reese84 sensor layer.
ImpervaUtmvcTokenProxyLess: the ___utmvc challenge layer.

Supported Providers

Provider	Price per 1,000	Routing
TwoCaptcha	$2.99
CapMonster	$2.00
Solverify	$0.80

Request Schema

Field	Type	Required	Description
`clientKey`*	string	Yes	Your API key. Create one in the AnySolver dashboard. Example: `your-api-key-from-dashboard`
`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 page where the CAPTCHA is displayed. Example: `https://www.example.com/login`
`incapsulaScriptUrl`*	string	Yes	Absolute URL of the `/_Incapsula_Resource?SWJIYLWA=…` script the blocked page loads. It rotates, so read it from the response you were blocked on. Example: `https://www.example.com/_Incapsula_Resource?SWJIYLWA=719d34d31c8e3a6e6fffd425f7e032f3`
`incapsulaCookies`*	string	Yes	Cookie header from the blocked response, as `name=value; name=value`. Every `incap_ses_*` cookie must be included. Example: `incap_ses_1263_1979199=Xt5eZ…; visid_incap_1979199=8w0Y…`
`proxy`*	string \| object	Yes	View proxy configuration
`reese84UrlEndpoint`	string	No	Absolute URL of the reese84 sensor endpoint, taken from the `POST …?d=<domain>` the page makes. Needed when the site guards the page with reese84 as well. Example: `https://www.example.com/onalbaine-legeance-what-come/14167535692918208311`
`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: `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36`

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

Field	Type	Required	Description
`status`*		Yes	Task status: "processing", "ready", or "failed". Example: `ready`
`errorId`*		Yes	0 = success, 1 = external error, 2 = internal error. Example: `0`
`taskId`	string	No	Unique identifier returned when the task was created. Example: `01KFNDF328KAN2AJ3BNHCQYE88`
`errorCode`		No	Machine-readable error code. Example: `CAPTCHA_UNSOLVABLE`
`errorDescription`	string	No	Human-readable error message with resolution hints. Example: `The captcha could not be solved.`
`cost`	number	No	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`	object	No	View solution properties

Solution Object Properties

The solution field contains an object with the following properties:

Field	Type	Required	Description
`cookies`*	Record<string, unknown>	Yes	Cookie jar to replay on the protected site, as a name → value map. Example: `{"reese84":"3:rVOfjx0PiH6yaKHP6NJA4A==:djhiQiEO06…"}`
`raw`*	Record<string, unknown>	Yes	Raw provider response data for advanced use cases.
`token`	string	No	The `reese84` cookie value. Set it on the protected domain before retrying the blocked request. Example: `3:rVOfjx0PiH6yaKHP6NJA4A==:djhiQiEO06…`
`userAgent`	string	No	User-Agent string used during solving (if applicable). Example: `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36`

ImpervaToken

Collecting the inputs

Proxyless alternatives

Supported Providers

Request Schema

Task Object Properties

Response Schema

Solution Object Properties

On this page

ImpervaToken

Collecting the inputs

Proxyless alternatives

Supported Providers

Request Schema

Task Object Properties

Response Schema

Solution Object Properties

On this page