Find the reCAPTCHA action on a page

1. 1.

   Inspect the relevant button or form

   Open browser developer tools and inspect the reCAPTCHA-bound button or form. Look for a data-action attribute; its value names the action for that element.

2. 2.

   Find the execution call

   Search the page’s JavaScript for grecaptcha.enterprise.execute or grecaptcha.execute. Read the action value in the options passed to the call.

3. 3.

   Follow the interaction you need

   A page can invoke different actions for different interactions. Follow the handler for the relevant button or form rather than copying the first action you find. If the action comes from a variable, use a debugger breakpoint to inspect its value when that handler runs.

// Classic v3:
grecaptcha.execute('PUBLIC_SITE_KEY', { action: 'login' });

// Enterprise score-based integration:
grecaptcha.enterprise.execute('PUBLIC_SITE_KEY', { action: 'login' });

// Here the action is login. Your page may use a different value.

In this example, the action is login. Names such as login and submit are examples, not values to guess. The website’s backend can validate the expected action, so a token generated for a different action may not satisfy the request.

Set site to the intended page’s hostname—not its full URL—and action to the exact value you found. A reCAPTCHA request also requires exactly one of proxy or proxyCandidates. Don’t add a type or url field.

The hostname must already have an active profile available to your workspace. Supplying site and action doesn’t create one; use site profile setup if it hasn’t been configured.

You don’t need the website owner’s verification secret. The public site key identifies the website’s Google integration; the verification secret belongs on its server. Neither replaces your solvethree workspace API key, which authenticates your API requests and must stay server-side.