Dedicated solverEnterprisereCAPTCHA v3 Solver API
Solve and bypass reCAPTCHA v3 through one stable REST API. Send the target details and get a ready-to-use solution back in seconds, without maintaining custom bypass logic.
How the reCAPTCHA v3 solver works
Google's invisible, score-based captcha and its Enterprise variant (RecaptchaV3Enterprise). We return a high-score token without any user interaction, ready to submit alongside your form or API request.
A predictable three-step flow that stays the same even when reCAPTCHA v3 changes its protection.
Send the site key and the page_action your target page passes to execute(). We return a token plus the matching _GRECAPTCHA cookie and browser fingerprint, so follow-up requests stay consistent.
Submit the target
Send the page URL and the challenge-specific fields in a single API request.
We handle the challenge
CaptchaSolv routes the task to a specialized solver and tracks it until completion.
Use the solution
Receive the token, headers, cookies, or sensor payload required by your next request.
reCAPTCHA v3 API request & response
The same endpoint and response envelope across every supported solver.
{
"api_key": "YOUR_API_KEY",
"type": "RecaptchaV3",
"site_url": "https://example.com/contact",
"data": {
"site_key": "6LcXXXXXXXXXXXXXXXXXXXXXX",
"page_action": "contact_submit"}
}{
"errorId": 0,
"status": "ready",
"solvtime": 1.38,
"data": {
"useragent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64)...",
"language": "en-US,en;q=0.9",
"solution": {
"token": "03AGdBq25SqKmv...",
"cookie": "_GRECAPTCHA=09AKhCRw..."}
}
}Task data fields
Fields you can send inside the data object of a solve request for this captcha type.
site_keyRequiredThe reCAPTCHA site key from the target page.
page_actionOptionalThe action string passed to execute(), e.g. "submit" or "homepage". Should match the page.
cookieOptionalAn existing _GRECAPTCHA cookie value to seed the solver session for cookie continuity across solves.
Solution fields
Fields returned in data.solution once the task is solved.
solution.tokenRequiredThe reCAPTCHA token to submit to the target site.
solution.cookieOptionalUpdated _GRECAPTCHA cookie from the solve session - send it with the token in follow-up requests.
What is reCAPTCHA v3?
reCAPTCHA v3 is Google's invisible, score-based captcha. There is no checkbox and no image puzzle: the script runs in the background on every page that loads api.js (or enterprise.js for reCAPTCHA Enterprise) and produces a token that Google turns into a risk score between 0.0 (very likely a bot) and 1.0 (very likely a human).
When the page calls grecaptcha.execute(siteKey, { action }), the script collects browser and interaction signals, sends them to Google together with the site key and the action name, and receives a token. The site forwards the token to its backend, which asks Google for the score through the siteverify API (or an Enterprise assessment) and then accepts, challenges or blocks the request. Google's default suggestion is a 0.5 threshold, but each site picks its own.
That is why reCAPTCHA v3 is hard to bypass with plain HTTP requests: there is nothing to click, the token is bound to the site key and action, it expires after about two minutes, and it is only useful if it carries a high score. Our reCAPTCHA v3 solver generates that token for you - your scraper or automation sends the site key and page_action, then submits the returned token the same way a real browser would.
- 01
Invisible script
The page loads api.js or enterprise.js with its site key - no widget is shown.
- 02
execute(action)
grecaptcha.execute() collects browser signals and requests a token for a named action.
- 03
Server-side score
The site sends the token to Google and gets back a 0.0-1.0 score and the action.
- 04
Allow or block
Requests below the site's threshold are blocked, challenged or flagged.
reCAPTCHA v3 parameters
site_keyKeyPublic key from the render= parameter of api.js or the first argument of grecaptcha.execute().
page_actionKeyAction name passed to execute(), e.g. login or submit - Google scores it and many sites check it.
tokenKeyValue the page sends to its backend, often as g-recaptcha-response or a custom JSON field.
_GRECAPTCHAGoogle cookie from the solve session - reuse it to keep the session consistent.
enterprise.jsLoaded instead of api.js on reCAPTCHA Enterprise sites - use RecaptchaV3Enterprise.
siteverifyGoogle endpoint the target's backend calls to read the score - you never call it yourself.
How to bypass reCAPTCHA v3 with the API
Bypassing reCAPTCHA v3 doesn't mean breaking Google's scoring - it means presenting a token that already carries a good score. With CaptchaSolv that takes four steps and no browser on your side.
- 01
Find the site key
Look for render=SITE_KEY in the api.js or enterprise.js script URL, or the first argument of grecaptcha.execute() in the page source.
- 02
Copy the page action
Find the action passed to execute(), e.g. { action: 'login' }, and send it as page_action so the token matches what the real page requests.
- 03
Create a RecaptchaV3 task
POST site_url, site_key and page_action to /solve - use RecaptchaV3Enterprise when the page loads enterprise.js - and poll until the status is ready.
- 04
Submit the token
Send solution.token in the field the site expects within two minutes, together with the returned user-agent and _GRECAPTCHA cookie.
reCAPTCHA v3 solver FAQ
Common questions about integrating this solver correctly.
Yes - it works on any site running reCAPTCHA v3 or reCAPTCHA v3 Enterprise, not just a fixed list of targets. Send the site key and page_action from the page you're hitting and we solve that site's specific challenge.
reCAPTCHA v3 never exposes its score directly - the target site checks it server-side against Google. We return a token that scores high enough to pass typical thresholds, which is what your request needs to submit alongside the form or API call.
Google's scoring takes the action name into account, so sending a page_action that doesn't match what the real page passes to execute() can lower the score the target site sees. Always copy the exact action string from the page's script.
Reuse solution.cookie together with the token when the site tracks the _GRECAPTCHA cookie across requests - it keeps the session consistent and can improve the score on subsequent solves for the same visitor.
Yes. Send the site key, page URL and page_action to the API and submit the returned token from your own HTTP client - no Selenium, Puppeteer or Playwright session is needed on your side.
Yes - use the RecaptchaV3Enterprise type for sites that load recaptcha/enterprise.js. The request and response shape is the same as for standard reCAPTCHA v3, so switching between the two only changes the type string.
Google expires reCAPTCHA tokens after about two minutes and each token can be verified only once, so request it right before you send the form or API call it protects.
Stuck trying to bypass reCAPTCHA v3?
Join our Discord and our team will help you get reCAPTCHA v3 solving working in your setup - free advice on handling it programmatically, even as the challenge changes over time.
Other solvers
Switch to a different captcha type we support.