ImpervaToken
Solve an Imperva (Incapsula) block through your own proxy and get the cookies to replay. Shows the request schema, an example and provider prices.
ImpervaToken solves an Imperva (Incapsula) block through your own proxy and returns the cookies that clear it. Imperva, formerly Incapsula, protects login, checkout and API endpoints with two challenge layers: the ___utmvc script and the reese84 sensor. The provider loads the challenge script through the proxy you give it.
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 (this task) |
| 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 |
The ___utmvc layer: the HTML loads /_Incapsula_Resource?SWJIYLWA=… | ImpervaUtmvcTokenProxyLess |
Send the proxy
task.proxy is required on this task type, and the provider solves from that address. The proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve. Request the protected page through the same proxy, and keep the same User-Agent while you trigger the block, solve and replay the cookies. Match your TLS fingerprint and header order to a real browser, because correct cookies from a mismatched client are still refused.
Find the parameters
Request the protected page through the proxy that you pass to the task, and keep the cookies of the blocked
response. Pass them as incapsulaCookies in the form name=value; name=value, including visid_incap_*,
nlbi_* and every incap_ses_* cookie.
Read the challenge script URL from that response: the src that matches /_Incapsula_Resource?SWJIYLWA=….
Pass it as incapsulaScriptUrl. The parameters are generated dynamically, so read them fresh on every block.
If the site also guards the page with reese84, pass reese84UrlEndpoint: the request the page posts its sensor
to, which ends with ?d=<your-domain> in DevTools.
Use the cookies
Replay every cookie of solution.cookies on the blocked request, through the same proxy and with the returned solution.userAgent.
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 |
|---|---|---|
2Captcha | $2.99 | |
CapMonster | $2.00 | |
Solverify | $0.80 | |
VoidCaptcha | $1.90 |
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 page where the CAPTCHA is displayed. Example: |
incapsulaScriptUrl* | string | Yes | URL of the Example: |
incapsulaCookies* | string | Yes | Incapsula cookies of the session, as Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
reese84UrlEndpoint | string | No | URL of the reese84 sensor endpoint: the 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": "ImpervaToken",
"websiteURL": "https://www.example.com/login",
"incapsulaScriptUrl": "https://www.example.com/_Incapsula_Resource?SWJIYLWA=719d34d31c8e3a6e6fffd425f7e032f3",
"incapsulaCookies": "visid_incap_1584510=o/UvTkB5QueTUtQBoLdWYVGWS2gAAAAAQU...; nlbi_1584510=Mv20CSpoRh/WQODNRk7kTwAAAACRz85+N7F/WQIGhC...; incap_ses_958_1584510=WZSQFuVAs3NDeHYpMIBLDVuWS2gAAAAAX...",
"proxy": "http://user:pass@1.2.3.4:8080"
}
}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 |
|---|---|---|---|
cookies* | Record<string, unknown> | Yes | Cookies to replay on the protected site, as a name → value map. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
token | string | No | The Example: |
userAgent | string | No | User-Agent string used during solving. Example: |