Skip to Content
AnySolver logo
AnySolver
Token

FunCaptchaToken

Solve Arkose Labs FunCaptcha through your proxy from the public key and get the session token. Shows the request schema, an example and provider prices.

FunCaptchaToken solves an Arkose Labs FunCaptcha through your proxy and returns the session token. FunCaptcha asks the visitor to solve a short image puzzle, and the page receives a session token on success. The task takes the page URL and the Arkose public key.

Use this task when the site checks that the solve came from the same IP as your own requests. Otherwise use FunCaptchaTokenProxyLess, which takes the same parameters without a proxy. For widgets that load from a custom Arkose host with no visible element, use FunCaptchaInvisibleToken.

Find the parameters

Open the page with DevTools and read the key:

  • websitePublicKey is the data-pkey attribute of the FunCaptcha div element. If the page has an element named fc-token, the key is the value after pk= in its value. It is a UUID such as 6220FF23-9856-3A6F-9FF1-A14F88123F55.

Send the proxy

task.proxy is required on this task type, and the provider solves from that address. The proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve.

Optional parameters

  • funcaptchaApiJSSubdomain: send it when the page loads the widget from a custom subdomain such as client-api.arkoselabs.com rather than the default one. The surl value in fc-token shows the host in use.
  • data: some sites send an extra blob value with the challenge. A blob is valid for one challenge, so capture it from the page right before you create the task, wrap it as {"blob":"..."} with JSON.stringify, and send the string.
  • userAgent: the browser User-Agent to solve with. Use the same value for your later requests.
  • enablePOW: defaults to true. Set it to false to trade coverage for latency on targets that never ask for proof-of-work. Only WTFSolve reads it; other providers ignore it.
  • headers: browser headers mirrored on the solve request so it matches the fingerprint the blob was minted under. Only WTFSolve reads it; other providers ignore it, and the field description lists the accepted keys.

Use the token

solution.token is the full Arkose session token. It contains |-separated fields such as r=, pk= and surl=. Submit it where the page puts the value of the fc-token field, or pass it to the page's callback.

Some providers also return the userAgent they used. When the site binds the token to the browser, send your later requests with that same User-Agent. If the token is rejected, check that the proxy kept one IP for the whole solve, then that websitePublicKey and websiteURL come from the page that shows the widget.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
2Captcha
$1.45–$50.00
Anti-Captcha
$3.00
CapMonster
$1.10
SolveCaptcha
$2.99–$50.00
WTFSolve
$0.20
VoidCaptcha
$2.00

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

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:

FieldTypeRequiredDescription
type*
Yes
websiteURL*
URLYes

Full URL of the page where the CAPTCHA is displayed.

Example: https://2captcha.com/demo/funcaptcha

websitePublicKey*
stringYes

Arkose Labs public key. It is the data-pkey attribute of the FunCaptcha div, or the value after pk= in the fc-token field.

Example: 6220FF23-9856-3A6F-9FF1-A14F88123F55

proxy*
string | objectYes

Proxy the provider solves through, as a string or an object. See Proxy configuration.

View proxy configuration

Example: http://user:pass@1.2.3.4:8080

funcaptchaApiJSSubdomain
stringNo

Custom subdomain the page loads the Arkose Labs widget from, such as client-api.arkoselabs.com. Send it only when the page uses a custom one.

Example: client-api.arkoselabs.com

data
stringNo

Additional FunCaptcha payload, commonly the blob value, as a JSON string produced with JSON.stringify. Pass it exactly as captured from the page.

Example: {"blob":"BLOB_DATA_VALUE"}

userAgent
stringNo

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: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36

enablePOW
booleanNo

Solve the challenge with proof-of-work enabled. Defaults to true, which covers both proof-of-work and plain targets. Set it to false to trade coverage for latency on targets that never ask for proof-of-work. Only WTFSolve reads this field; other providers ignore it.

Example: true

headers
objectNo

Browser headers mirrored on the solve request so it matches the fingerprint the blob was minted under. Only the seven keys listed here are sent; anything else is dropped. When both this object and the top-level userAgent carry a User-Agent, userAgent wins. Only WTFSolve reads this field; other providers ignore it.

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "FunCaptchaToken",
        "websiteURL": "https://2captcha.com/demo/funcaptcha",
        "websitePublicKey": "6220FF23-9856-3A6F-9FF1-A14F88123F55",
        "proxy": "http://user:pass@1.2.3.4:8080"
    }
}

Optional fields are not guaranteed across providers

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
token*
stringYes

The solved CAPTCHA token to submit with your form.

Example: 142000f7f4545ca36.6123911001|r=us-beast-1|meta=3|metabgclr=%23ffffff|...|pk=6220FF23-9856-3A6F-9FF1-A14F88123F55|...

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.

userAgent
stringNo

User-Agent string used during solving.