A reCAPTCHA solving API is different from siteverify
No—Google's siteverify endpoint can't issue a reCAPTCHA response token. It validates a token supplied by a client. Enterprise assessments also evaluate an existing token; neither endpoint generates one from a site key.
On this page
Choose the API for the job you need
| API | What you supply | What you get |
|---|---|---|
| Google siteverify | An existing response token | A verification result |
| Google Enterprise assessments | An existing response token | An assessment of that token |
| solvethree tasks | A supported site's hostname, action, and proxy configuration | A task whose ready result contains a solution token |
In Google's reCAPTCHA v3 flow, the client SDK produces a response token and the site owner's backend validates it with siteverify. In the Enterprise flow, the client SDK produces the token and the backend creates an assessment.
If you're adding verification to a site you own, use the appropriate Google flow. If you need a solving service for a supported target, use solvethree's task API. The solver supplies a token for the target to evaluate; it doesn't replace the target's verification.
What a real solver request looks like
First, make sure the target site has an active profile available to your workspace. Sending a hostname and action doesn't create one. Use site profile setup if that prerequisite isn't complete.
Create the task with POST /v1/tasks on the solvethree API, using Authorization: Bearer followed by your workspace API key. Keep that key on your server.
{
"site": "accounts.example.com",
"action": "login",
"proxy": "http://user:[email protected]:8080",
"requestId": "example_login_001"
}Replace the example hostname, action, and proxy with the values for your target request. site is a hostname, not a full URL. reCAPTCHA requests require exactly one of proxy or proxyCandidates; don't add type or url. This example uses the default recaptchaType, enterprise-v3; the gateway also accepts v3.
Retrieve the task with GET /v1/tasks/:id. Keep polling while its status is pending or solving. Only ready contains a usable solution. If it becomes failed, stop polling and inspect errorCode and error.
Don't spend an Enterprise token on a test assessment
Google documents that Enterprise website response tokens expire after two minutes and can be assessed only once. Request the solve near the protected request. Creating an assessment merely to check whether the token works can consume it before the intended target uses it.
Submit solution.token to the intended target—not the task ID. Use the returned userAgent and secChUa browser identity, together with the proxy that succeeded during solving. Switching proxies or mixing unrelated browser headers can break the subsequent request.
A ready task means a solution is available, not that the target has accepted your application request. Judge acceptance from the target's response, not from task creation or readiness.
Sources and API reference
Run your first task.
Start with $5 in workspace credit.