Why solvethree uses a site profile instead of a websiteKey field

1. 1.

   Open Add a site

   Go to Site profiles and select Add a site. Enter the target's HTTPS Page URL. The task will use its hostname, not this full URL. Supply the optional Navigation URL and Referer value if needed for the page setup.

2. 2.

   Choose the type and check the Site key

   Select Enterprise v3 for a reCAPTCHA Enterprise integration, or Regular v3 for regular reCAPTCHA v3. The form can auto-discover the Site key; you can supply an override in the optional Site key field.

3. 3.

   Set the Capture action

   Capture action is required. For the request below, configure a profile with the capture action login. Reviewed system profiles can fill the known page setup and capture action without a live pull; read the form's explanation of the chosen action.

4. 4.

   Submit and wait for active

   Select Add site. Submissions may pass through queued, capturing, validating or review states before becoming active; there's no guaranteed capture duration. Some accounts show Add credit to continue. If capture fails, inspect its reason before retrying.

Use one profile per hostname, capture action and reCAPTCHA type. An exact execution-action match selects its profile. Other execution actions require one unambiguous capture target, so don't assume a single profile for a hostname covers every action.

Once the profile is active, send this object directly as the JSON body to POST /v1/tasks. Authenticate with Authorization: Bearer followed by your workspace API key, and keep that key on the server.

{
  "site": "accounts.example.com",
  "action": "login",
  "proxy": "http://user:[email protected]:8080",
  "requestId": "example_login_001"
}

• site is the hostname: no scheme, path or query. The full Page URL belongs in the console profile.
• action is the execution action for this task. Here, login matches the capture action configured above.
• proxy supplies the proxy for the solve. Exactly one of proxy or proxyCandidates is required; don't send both.
• requestId is optional. If creation times out, resending the same request with the same ID returns the existing task. Changing task inputs while reusing that ID conflicts.

Don't carry over websiteKey, websiteURL, type or url from the previous API's request shape. For reCAPTCHA, recaptchaType defaults to enterprise-v3, which is why the example omits it. Regular v3 uses recaptchaType set to v3.