Skip to Content
AnySolver logo
AnySolver
Token

ReCaptchaMobileToken

Get a reCAPTCHA Enterprise token for an Android app through your own proxy. Covers the request schema, an example and each provider's price per 1,000.

ReCaptchaMobileToken solves the reCAPTCHA Enterprise check of an Android app through your proxy and returns the token. Android apps run this check through Google's com.google.android.recaptcha SDK instead of loading the web widget. A token minted for a web sitekey fails a mobile check, and the reverse. For websites, use ReCaptchaV3EnterpriseToken or ReCaptchaV2EnterpriseToken.

Use ReCaptchaMobileTokenProxyLess when the token does not have to come from a specific network.

Use your 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. Send the token to the app's backend from the same address.

Find the parameters

All three values come from the app, not from a web page. Read them from the app's call to the reCAPTCHA SDK or from its network traffic.

  • websiteKey: the Enterprise sitekey the app was built with.
  • appPackageName: the Android package name, such as com.example.app. Google ties a mobile key to its package, so a wrong package scores badly even when a token comes back.
  • pageAction: the action the app passes to the SDK, such as login. It must match exactly.

Optional parameters

deviceOptions selects the device profile the token is minted from. Providers that do not support an option ignore it.

  • deviceOptions.model: pins one device model from the provider's pool, for example Pixel_7_Pro.
  • deviceOptions.randomDevice: rotates profiles on every solve.
  • deviceOptions.platform: the mobile platform to imitate. Only android is supported.

Use the token

Send the token to the app's backend the way the app would, with the solution.userAgent that comes back with it. If the backend rejects the token, check that the proxy kept one IP for the whole solve, then that appPackageName and pageAction match the app.

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

Supported Providers

ProviderPrice per 1,000Routing
VoidCaptcha
$1.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
websiteKey*
stringYes

reCAPTCHA Enterprise sitekey the Android app was built with. Mobile keys are separate from web keys: a web token fails a mobile check and the reverse.

Example: 6LfXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

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

appPackageName
stringNo

Android package name of the app, such as com.example.app. Google ties a mobile key to its package, so a wrong package scores badly even when a token comes back.

Example: com.example.app

pageAction
stringNo

Action the app passes to the reCAPTCHA SDK, such as login. It must match exactly or verification fails.

Example: login

deviceOptions
objectNo

Device profile the token is minted from. Not every provider supports every option; unsupported ones are ignored.

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "ReCaptchaMobileToken",
        "websiteKey": "6LfXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
        "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: 03AFcWeA4mZ...

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.

userAgent
stringNo

User-Agent the token was minted under. Send the token downstream with this exact User-Agent.