ImpervaUtmvcTokenProxyLess
Solve the Imperva (Incapsula) UTMVC challenge and get the ___utmvc cookie value to set and activate. Shows the request schema, an example and provider prices.
ImpervaUtmvcTokenProxyLess solves the Imperva UTMVC challenge and returns the ___utmvc cookie value. UTMVC is an Imperva challenge layer: the page loads an obfuscated /_Incapsula_Resource?SWJIYLWA=… script, and when the script runs correctly it sets a ___utmvc cookie that authorizes the session. This task runs the script and returns the cookie value.
You are dealing with UTMVC when the HTML loads a script that matches src="/_Incapsula_Resource?SWJIYLWA=…". It is separate from reese84, and some sites run both.
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 |
The ___utmvc layer: the HTML loads /_Incapsula_Resource?SWJIYLWA=… | ImpervaUtmvcTokenProxyLess (this task) |
Activate the cookie
solution.utmvc as the ___utmvc cookie on the protected domain.Send a GET to /_Incapsula_Resource?SWKMTFSR=1&e=<random> on the same domain, where e is a random float such
as 0.14896897949050825. If the cookie is valid, the server answers by setting the cookie to the value a
with a max-age of 0.
The cookie name is ___utmvc, with three leading underscores, not __utmvc.
Use the same User-Agent, header order and TLS fingerprint for the script fetch, the activation request and every request after it. Send the solution.userAgent if you did not set userAgent on the task.
When trust is low, Imperva can replace the script challenge with a PopularCaptcha or GeeTest challenge in an iframe. This task does not solve that challenge: solve it with the task type for that CAPTCHA.
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: |
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": "ImpervaUtmvcTokenProxyLess",
"websiteURL": "https://group.accor.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 |
|---|---|---|---|
utmvc* | string | Yes | The Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent string used during solving. Example: |