Frequently asked questions
Do you guarantee the reCAPTCHA score?
No, and nobody honestly can. minScore is a client request accepted for contract compatibility. A ready task proves that Google issued a token; success on the target site remains the final oracle. Our per-page validation targets exactly that success.
Why is my page not accepted?
The API only serves pages in the validated registry. If you receive ERROR_PROFILE_NOT_VALIDATED, check the exact URL, the sitekey, the action and the Enterprise mode, or request validation of your page. The rejection uses no slot and is not billed.
Can I reuse a token?
No. A reCAPTCHA v3 token cannot be replayed and expires about two minutes after it is issued. Every business submission requires a new task. Fetch the result and use it immediately.
What happens when Google ships a new release?
Tasks receive ERROR_RELEASE_NOT_VALIDATED until the new release is validated. We would rather reject than issue a token that will be refused. The status page shows the release currently being validated.
Do I need to provide a proxy?
No, and you can't: every task runs as RecaptchaV3TaskProxyless and goes out through our own managed pool — nothing to configure, and no client-supplied egress option.
Where are my tokens and my key stored?
Nowhere. The key is checked in memory, task parameters are not logged, the token stays 90 seconds in memory and then disappears. Only metadata (ID, status, timestamps, error code) is kept in the database.
What is the capacity?
Each key can run several tasks in parallel (2 by default). Beyond that, ERROR_NO_SLOT_AVAILABLE tells you to retry as soon as a task completes — expect 5 to 20 seconds per task. Need more concurrency or reserved slots? Contact us.
My integration already uses createTask / getTaskResult, what do I need to change?
The base URL. The createTask and getTaskResult routes, fields and error codes are identical within the supported scope. Remove the fields we do not accept (callback, softId, proxy). Migration guide →