ImpervaUtmvcTokenProxyLess
Solve the Imperva / Incapsula UTMVC challenge and get the ___utmvc cookie value to set and activate.
UTMVC is Imperva's rotating challenge layer: the page loads an obfuscated /_Incapsula_Resource?SWJIYLWA=… script which, when executed correctly, authorises the session through a ___utmvc cookie. This task runs that script and returns the cookie value.
A site is on UTMVC when its HTML loads a script matching src="/_Incapsula_Resource?SWJIYLWA=…". It is a separate layer from reese84: some sites run one, some run both.
Activating the cookie
solution.utmvc as the ___utmvc cookie on the protected domain.GET /_Incapsula_Resource?SWKMTFSR=1&e=<random> on the same domain, where e is a random float such as
0.14896897949050825. A valid cookie is acknowledged by the server clearing it (value a, max-age 0).
Three underscores
The cookie name is ___utmvc, not __utmvc. This is the single most common integration bug on this challenge.
Keep the fingerprint consistent
Use the same User-Agent, header order and TLS fingerprint across the challenge fetch, the submit request and every
request that follows. Send the userAgent from the solution if you did not pin one on the task.
Sessions can escalate
When trust drops, Imperva swaps the script challenge for an hCaptcha or GeeTest iframe. That block is a different problem and is not solved by this task: refresh the session or lower request pressure instead.
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: |
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": "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 | 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 |
|---|---|---|---|
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 (if applicable). Example: |