Test solvethree in Postman

1. 1.

   Import the downloaded JSON

   In Postman, choose Import and select the collection file. It contains Create task and Retrieve task with inherited Bearer authorization and variable placeholders.

2. 2.

   Check the site's profile

   Your workspace needs an active profile for the target hostname. Configure it in the console before testing; sending a hostname and action doesn't create a profile. See site profile setup.

3. 3.

   Configure private environment values

   Create and select an environment for this test. Populate the values below privately, including any proxy credentials. Don't put secrets directly in the collection or export populated secrets.

4. 4.

   Configure Bearer authorization

   At collection level, select Bearer Token and reference a private environment variable containing your workspace API key. Leave both requests set to inherit authorization. The API expects Authorization: Bearer followed by that key.

Open Create task. It sends POST to https://api.solvethree.com/v1/tasks with a raw JSON body populated from your selected environment.

{
  "site": "{{SITE}}",
  "action": "{{ACTION}}",
  "proxy": "{{PROXY}}",
  "requestId": "{{REQUEST_ID}}"
}

This request uses reCAPTCHA Enterprise v3 by default. Don't add a type or url field. It supplies a single proxy, so don't also add proxyCandidates: exactly one of those fields is required.

Set REQUEST_ID before sending, then click Send once. Check the HTTP response first. If it's non-successful, inspect the request error rather than treating the body as a successful task response. Fix invalid inputs instead of repeatedly sending them unchanged.

For a successful creation response, copy the returned id into your private TASK_ID environment value. Don't click Create task again just to check progress.

Open Retrieve task and confirm that TASK_ID contains the returned task ID. This request uses GET /v1/tasks/:id on the same API. Send it manually, check the HTTP response, then inspect the task's status.

HTTP 200 or 201 alone doesn't mean a solution is ready; only status: ready does. This manual test checks task creation and retrieval, not whether the target website accepts the result.

If you continue by submitting the reCAPTCHA token to its intended target, use the returned userAgent and secChUa browser identity and the successful proxy. Don't switch IPs or mix in an unrelated browser identity. A ready token can still be rejected by the target.

A connection timeout doesn't prove that creation failed. If you have the task ID, retrieve it. If you never received the ID, resend Create task with the same REQUEST_ID and unchanged task inputs. That recovers the existing task instead of creating another logical task.

Don't generate a fresh REQUEST_ID just because the response was lost. Reusing an ID with different task inputs conflicts; use a new ID when you deliberately start a new task.