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 ascom.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 aslogin. 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 examplePixel_7_Pro.deviceOptions.randomDevice: rotates profiles on every solve.deviceOptions.platform: the mobile platform to imitate. Onlyandroidis 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
| Provider | Price per 1,000 | Routing |
|---|---|---|
VoidCaptcha | $1.00 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in a workspace of the AnySolver dashboard. Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See Tasks for per-task schemas. View task properties |
settings | object | No | 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:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
websiteKey* | string | Yes | 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: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
appPackageName | string | No | 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: |
pageAction | string | No | Action the app passes to the reCAPTCHA SDK, such as login. It must match exactly or verification fails. Example: |
deviceOptions | object | No | 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
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes |
Example: | |
taskId | string | No | Unique identifier returned when the task was created. Example: |
errorCode | No | Machine-readable error code. Example: | |
errorDescription | string | No | Human-readable error message with resolution hints. Example: |
cost | number | No | Actual cost charged for this task in USD. Example: |
taskType | No | The type of CAPTCHA task to solve. Example: | |
provider | No | Provider that handled this task. While processing, the provider currently solving it. Example: | |
solution | object | No |
Solution Object Properties
The solution field contains an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
token* | string | Yes | The solved CAPTCHA token to submit with your form. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent the token was minted under. Send the token downstream with this exact User-Agent. |