Skip to content

Use code FUN10 for 10% bonus credits

DocsIncapsula (reese84)

Incapsula reese84 API Reference

Get the Incapsula reese84 cookie and replay it.

Read Markdown (English)

The Captcha.fun Incapsula (reese84) API accepts kind, url and returns reese84 cookie. Send the API_KEY header, create a solve with POST /v1/request, then poll GET /v2/response/{id} until ready is true.

What you’ll need

  • Your API key
  • The URL of the page where the challenge appears
  • Optional: jsUrl
  • A proxy, if the result must come from your own IP (reese84_proxy)
Use kind

Good to Know

Returns the reese84 cookie for the protected page. The sensor script is located automatically; pass jsUrl only when it cannot be found.

Send the Challenge

Send the page details with your API key. You get a solve id back right away.

POSThttps://api.captcha.fun/v1/request
curl -X POST https://api.captcha.fun/v1/request \
  -H "API_KEY: CAPFUN-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
  "kind": "reese84",
  "url": "https://your-domain.example"
}'

Response

Returns the solve id. Use it to get the result.

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "message": "Started Solving"
}
Request fields5 body fields · 2 required

Headers

NameTypeRequiredDescription
API_KEYstringYesYour API key
Content-TypestringYesapplication/json
APP_IDstringNoOptional app ID for request tracking

Body

NameTypeRequiredDescription
kindstringYesOne of reese84, reese84_proxy
urlstringYesPage URL where the challenge appears
jsUrlstringNoSensor script URL. Found on the page if omitted
proxystringNoFor _proxy kinds: host:port or host:port:username:password
platformstringNoRequested platform label: windows (default) or mac

Wait for the Result

Use the solve id to fetch the result.

GEThttps://api.captcha.fun/v2/response/{id}

Poll every second until ready is true.

Example

curl -X GET https://api.captcha.fun/v2/response/550e8400-e29b-41d4-a716-446655440000 \
  -H "API_KEY: CAPFUN-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
  -H "Accept: application/json"

Response

{
  "ready": true,
  "status": "SUCCESS",
  "success": true,
  "userAgent": "RETURNED_USER_AGENT",
  "secUa": "RETURNED_SEC_CH_UA",
  "token": "5E6F7G8H9I0J1K2L3M4N5O~0~...,",
  "cookies": {
    "reese84": "5E6F7G8H9I0J1K2L3M4N5O~0~...,"
  },
  "cookieHeader": "reese84=5E6F7G8H9I0J1K2L3M4N5O~0~...,"
}
Request and response fields9 response fields

Request

NameTypeRequiredDescription
idstring (UUID)YesPath parameter. The id from Create Solve
API_KEYstringYesHeader. Your API key

Response Fields

NameTypeRequiredDescription
readyboolean—true when the solve is finished (v2 only)
statusstring—PENDING while solving, then SUCCESS or FAILURE
successboolean—Whether the solve succeeded
userAgentstring—Value to send as User-Agent when using the result. Preserve it exactly
secUastring—Value to send as Sec-CH-UA when using the result
tokenstring—The minted reese84 cookie value
cookiesobject—The defense cookie family, cookie name to value
cookieHeaderstring—The solving session's full Cookie header value, verbatim — replay it with the returned userAgent from the same egress IP
messagestring—Failure reason. Omitted on success

Send the Cookies

Send it as the reese84 cookie on requests to the protected site, with the returned userAgent and from the same IP as the solve.

When using a successful result, preserve the returned userAgent as User-Agent and secUa as Sec-CH-UA.

Wrong or rejected result? Report the failed solve.

More from Imperva