Configure profiles for more than one reCAPTCHA action
For login and checkout on the same hostname, create an active profile for each capture action and reCAPTCHA type. Then send each task with the corresponding action. A hostname alone isn't enough to select the right profile.
On this page
Create the login and checkout profiles
In Site profiles, configure one profile per hostname, capture action and reCAPTCHA type. For this example, both profiles use accounts.example.com and Enterprise v3.
- 1.
Add the login profile
Choose Add a site. Enter the HTTPS Page URL where the login action runs, select Enterprise v3, and set Capture action to
login. The form also supports optional Navigation URL, Site key and Referer values. Submit with Add site. - 2.
Add the checkout profile
Repeat for the checkout page on the same hostname, keeping Enterprise v3 and setting Capture action to
checkout. - 3.
Confirm both profiles are active
An active profile must be available to your workspace before solving. If a capture fails, inspect the displayed reason before retrying. Sending a task with a hostname and action doesn't create the missing profile.
Send a separate task for each action
Send each object below as a separate POST /v1/tasks request. Authenticate with your workspace API key using Authorization: Bearer, and keep that key on the server.
[
{
"site": "accounts.example.com",
"action": "login",
"proxy": "http://USER:PASSWORD@PROXY:PORT",
"requestId": "login-flow-001"
},
{
"site": "accounts.example.com",
"action": "checkout",
"proxy": "http://USER:PASSWORD@PROXY:PORT",
"requestId": "checkout-flow-001"
}
]Replace the hostname and proxy placeholder with your target hostname and proxy URL. Each request supplies one proxy; don't also add proxyCandidates. The omitted recaptchaType defaults to enterprise-v3. Don't add type or url fields to these reCAPTCHA requests.
The two requestId values identify separate logical tasks. Use a new ID for a new solve. If task creation times out, reuse the same ID with the same request to recover the existing task; reusing an ID with different inputs conflicts.
When the execution action doesn't match
For the matching hostname and reCAPTCHA type, an exact execution action selects its profile: login selects the login profile, and checkout selects the checkout profile.
A different execution action requires one unambiguous captured target. If more than one target is possible, don't assume solvethree chooses an arbitrary profile. Use the configured capture action when possible. If selection is reported as ambiguous, compare the task's hostname, reCAPTCHA type and action with the profiles in the console, and use the actual console/API response to diagnose the mismatch.
A unique site key for every action isn't the routing rule. Configure the profiles by hostname, capture action and reCAPTCHA type rather than trying to distinguish actions through site keys.
Sources and API reference
Run your first task.
Start with $5 in workspace credit.