Imperva Incapsula Solver API: reese84 and utmvc Cookies

Choose the mode that matches the target challenge, and do not mix up the script URLs. Reese84 requires websiteURL,reeseScriptUrl; UT.mvc requires websiteURL,isUtmvc:true,scriptURL, where scriptURL is the full URL of /_Incapsula_Resource?SWJIYLWA=.... Both modes accept an optional HTTP proxy, useragent, and language; cookies can be used to preset browser cookies, and each item may contain only name,value.

Browser selection

When providing useragent, use desktop Chrome/Chromium or Android Chrome. Firefox, Edge, Opera and iOS are unsupported. Android support depends on whether a compatible device fingerprint can be generated.

Request fields

The top-level type and task are required; all task.* paths below are inside the task object. Field names are case-sensitive. Length limits are measured in UTF-8 bytes.

Reese84 request:

Create request example

{
  "type": "imperva",
  "task": {
    "websiteURL": "https://example.com/protected",
    "reeseScriptUrl": "https://example.com/challenge/reese.js"
  }
}

cURL call

Replace the key, site details, and proxy in the example with your actual values; keep the Idempotency-Key unchanged for the same business request.

curl -sS -X POST 'https://www.tiam.codes/v1/tasks' \
  -H 'Authorization: Bearer sh_REPLACE_ME' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: example-imperva-0001' \
  --data-binary @- <<'JSON'
{
  "type": "imperva",
  "task": {
    "websiteURL": "https://example.com/protected",
    "reeseScriptUrl": "https://example.com/challenge/reese.js"
  }
}
JSON

UT.mvc request:

{
  "type": "imperva",
  "task": {
    "websiteURL": "https://example.com/protected",
    "isUtmvc": true,
    "scriptURL": "https://example.com/_Incapsula_Resource?SWJIYLWA=example"
  }
}

cURL call

Replace the key, site details, and proxy in the example with your actual values; keep the Idempotency-Key unchanged for the same business request.

curl -sS -X POST 'https://www.tiam.codes/v1/tasks' \
  -H 'Authorization: Bearer sh_REPLACE_ME' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: example-imperva-0001' \
  --data-binary @- <<'JSON'
{
  "type": "imperva",
  "task": {
    "websiteURL": "https://example.com/protected",
    "isUtmvc": true,
    "scriptURL": "https://example.com/_Incapsula_Resource?SWJIYLWA=example"
  }
}
JSON

Create response and polling

A successful create returns HTTP 202, and status is usually queued initially. Save the taskId and call GET /v1/tasks/{taskId} about every 2–3 seconds. The soft processing time limit for this type is 180 seconds; after the soft limit the task may enter uncertain, and the results of accepted tasks can still be verified. Clients should not blindly recreate the task with a new Idempotency-Key.

Result fields

Read solution only when status=completed; the table below lists common fields, and the actual fields are determined by the task response.

The result contains solution.cookies and solution.useragent; Reese84 commonly yields reese84, UT.mvc commonly yields ___utmvc, and other session cookies may also be included. Example result: {"cookies":{"reese84":"EXAMPLE_COOKIE"},"useragent":"Mozilla/5.0 ..."}. Subsequent requests should reuse the complete cookie set, the returned User-Agent, and the proxy egress used during solving.

Failures and troubleshooting

Do not mix the Reese84 and UT.mvc script fields. When submitting cookies, each item must have exactly name,value; provide the proxy address and port together.

Common errors for create requests are 400 INVALID_TASK, 402 INSUFFICIENT_BALANCE, 429 TASK_LIMIT_EXCEEDED, and 503 TYPE_UNAVAILABLE. When a created task fails, the public error code is TASK_FAILED or TASK_TIMEOUT; uncertain corresponds to TASK_UNCERTAIN. See the Platform API reference for details.

The processing window starts after task creation is confirmed; queue waiting does not consume it. The current node timeout is approximately 120 seconds; the platform allows a 180-second soft window for transport and result polling.

Supported User Agents