FunCaptcha Solver API for Authorized Arkose Labs Testing

Availability notice: Arkose FunCaptcha changes its detection and challenges very frequently, so the solve rate may drop at any time and solving may be completely unavailable for short periods. Availability and success rate are not guaranteed for this type; do not rely on it for business that requires high availability. Failed tasks are not charged and the reserved amount is fully refunded; build retries and fallbacks into your integration.

Use SolveHub to create an Arkose Labs FunCaptcha task for a website and workflow you are authorized to test. A task requires a proxy, challengeInfo and browserInfo collected from the same real challenge. After the task completes, read the Arkose token from solution.solution.

FunCaptcha challenges and detection change frequently. Availability and success rates are not guaranteed, so check live status before creating a task and plan a fallback for tests that cannot wait. Failed tasks are not charged. Every value should come from your real page and browser; fabricated values are usually detected or fail outright.

FunCaptcha API at a Glance

• Required input: a proxy URL, challengeInfo and browserInfo.
• Create request: POST /v1/tasks with type funcaptcha and an Idempotency-Key.
• Polling: save taskId and check GET /v1/tasks/{taskId} about every 2–3 seconds.
• Completed result: read the token from solution.solution, not solution.value.
• Availability: check the current price and status before submitting; do not assume a task type is always available. See live prices.

Request fields

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

challengeInfo fields

41 fields, 12 of them required. Omit an optional field to use the default behavior; when sent it must have the listed type, otherwise the create request returns 400 INVALID_TASK. Fields not listed are rejected.

browserInfo fields

16 fields, 5 of them required (User-Agent, Linux, Mac, Mobile, Safari). User-Agent, Sec-Ch-Ua, Accept-Language, etc. should come from the same real browser and match the platform flags.

Create request example

The example below contains only the required fields and common headers. All values are placeholders and must be replaced with real values from your page.

{
  "type": "funcaptcha",
  "task": {
    "proxy": "http://user:pass@203.0.113.10:8080",
    "challengeInfo": {
      "publicKey": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
      "site": "https://example.com",
      "surl": "https://example.arkoselabs.com",
      "capiMode": "lightbox",
      "styleTheme": "default",
      "locationHref": "https://example.com",
      "documentReferrer": "https://example.com",
      "ancestorOrigins": [
        "https://example.com"
      ],
      "treeIndex": [
        0
      ],
      "treeStructure": "[[]]",
      "languageEnabled": true,
      "jsfEnabled": true
    },
    "browserInfo": {
      "Accept-Language": "en-US,en;q=0.9",
      "Linux": false,
      "Mac": false,
      "Mobile": false,
      "Safari": false,
      "Sec-Ch-Ua": "\"Chromium\";v=\"152\", \"Not?A_Brand\";v=\"24\", \"Google Chrome\";v=\"152\"",
      "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36"
    }
  }
}

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-funcaptcha-0001' \
  --data-binary @- <<'JSON'
{
  "type": "funcaptcha",
  "task": {
    "proxy": "http://user:pass@203.0.113.10:8080",
    "challengeInfo": {
      "publicKey": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
      "site": "https://example.com",
      "surl": "https://example.arkoselabs.com",
      "capiMode": "lightbox",
      "styleTheme": "default",
      "locationHref": "https://example.com",
      "documentReferrer": "https://example.com",
      "ancestorOrigins": [
        "https://example.com"
      ],
      "treeIndex": [
        0
      ],
      "treeStructure": "[[]]",
      "languageEnabled": true,
      "jsfEnabled": true
    },
    "browserInfo": {
      "Accept-Language": "en-US,en;q=0.9",
      "Linux": false,
      "Mac": false,
      "Mobile": false,
      "Safari": false,
      "Sec-Ch-Ua": "\"Chromium\";v=\"152\", \"Not?A_Brand\";v=\"24\", \"Google Chrome\";v=\"152\"",
      "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36"
    }
  }
}
JSON

Create response and polling

A successful create returns HTTP 202, and status is usually queued at first. Save the taskId and call GET /v1/tasks/{taskId} about every 2–3 seconds. The soft time limit for this type is 180 seconds. While solving, the status is dispatching or processing; when finished it is completed or failed. A task that still has no result after the time limit becomes uncertain; keep polling the original task and do not recreate it with a new idempotency key.

Result fields

When status=completed, solution is an object:

Successful response example:

{
  "taskId": "5a1c6c55-7f3b-4c5d-9a7e-2f0d8e1b9c21",
  "type": "funcaptcha",
  "status": "completed",
  "priceMicros": 2000,
  "traceId": "0f3b2d7e-91a4-4c62-8a51-7d2e9c4b1f08",
  "solution": {
    "gameInfo": {
      "gameType": 4,
      "solveTime": 0.32,
      "variant": "silent_pass",
      "waves": 0
    },
    "solution": "XXXXXXXXXXXXXXXXX.XXXXXXXXXX|r=eu-west-1|meta=3|metabgclr=transparent|metaiconclr=%23757575|maintxtclr=%23b8b8b8|guitextcolor=%23474747|pk=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX|at=40|sup=1|rid=1|ag=101|cdn_url=https%3A%2F%2Fexample.arkoselabs.com%2Fcdn%2Ffc|surl=https%3A%2F%2Fexample.arkoselabs.com|smurl=https%3A%2F%2Fexample.arkoselabs.com%2Fcdn%2Ffc%2Fassets%2Fstyle-manager"
  },
  "createdAt": "2026-10-13T08:00:00Z",
  "finishedAt": "2026-10-13T08:00:06Z"
}

Failed response example:

{
  "taskId": "5a1c6c55-7f3b-4c5d-9a7e-2f0d8e1b9c21",
  "type": "funcaptcha",
  "status": "failed",
  "priceMicros": 2000,
  "traceId": "0f3b2d7e-91a4-4c62-8a51-7d2e9c4b1f08",
  "errorCode": "TASK_FAILED",
  "failureReason": "Too many waves to solve, make skipHighWaves false in challengeInfo to solve anyway",
  "createdAt": "2026-10-13T08:00:00Z",
  "finishedAt": "2026-10-13T08:00:04Z"
}

Failures and troubleshooting

A failed task (status=failed) is not charged and the reserved amount is fully refunded; failureReason gives the specific reason returned by the solving service. Common reasons and fixes:

Use a new Idempotency-Key when resubmitting (the same key returns the original failed task). If a field type or required field is invalid, the create request returns 400 INVALID_TASK directly, with no task and no charge.

Common create-request errors 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 maps to TASK_UNCERTAIN. See the Platform API Reference for details.