Test the CAPTCHA API in Insomnia

You need a workspace API key, an active profile for the target site, and a proxy. Set up the site profile before sending the task: supplying a hostname and action doesn’t create one.

Use a private local environment named solvethree-local with the variables below. These are names chosen for this walkthrough, not additional API fields. Keep the API key and proxy credentials out of shared configurations.

1. 1.

   Configure the create request

   Create a POST request using api_base followed by /tasks. Add the query parameter waitMs with value 0. Select Bearer authentication and supply api_key as the token; the request must send an Authorization header using the Bearer scheme.

2. 2.

   Build the JSON body

   Choose a JSON body containing site, action, proxy, and requestId. Populate the first three from their matching local variables and requestId from request_id. Send exactly one of proxy or proxyCandidates; this walkthrough uses proxy. Don’t add type or url. Omitting recaptchaType selects the default, enterprise-v3.

3. 3.

   Send and inspect the response

   Check the HTTP response before reading it as a successful task payload. If creation succeeds, copy the returned task ID into task_id. Keep the task body and request_id available in case you need to recover the request.

4. 4.

   Retrieve that task

   Create a GET request using api_base followed by /tasks/ and the copied task ID. Set waitMs to 15000, use the same Bearer key, and leave the body empty. Copy the ID manually; this walkthrough doesn’t depend on a response-chaining expression.

Create task
  Method: POST
  URL: https://api.solvethree.com/v1/tasks?waitMs=0
  Auth: Bearer Token — your private workspace key
  Body: JSON — site, action, proxy and a stable requestId

Retrieve task
  Method: GET
  URL: https://api.solvethree.com/v1/tasks/PASTE_RETURNED_ID?waitMs=15000
  Auth: Bearer Token — the same workspace key
  Body: none

Keep the task's proxy in the JSON body. Insomnia's own network proxy setting
controls its API connection, not the proxy used to generate/submit the solution.

The HTTP request returns a non-success response.

Inspect the HTTP error before trying to read a successful task payload.

Try this: Correct the reported request or authentication problem. Don’t repeatedly submit unchanged invalid inputs or assume every error means insufficient credit.

The task is pending or solving.

Neither status contains a usable solution.

Try this: Send the GET request again for the same task ID. Don’t create another task just because this one hasn’t finished.

The task is failed.

Read errorCode and error; site-unreachable is one possible task error.

Try this: Stop retrieving that task and address the reported cause before starting another. Failed solves are refunded.

The create request times out without returning an ID.

A connection timeout doesn’t prove that creation failed.

Try this: Resubmit the same task body with the same requestId to recover the existing task. Changing inputs while reusing that ID causes a conflict.

A ready reCAPTCHA task provides a token. If you submit it to the target, use the returned userAgent and secChUa with the same proxy used for solving. A ready response confirms that a solution was generated—not that your application request succeeded.