Legacy paths
Get the answer of a job (legacy path)
NopeCHA's original poll path: GET /?id=. Errors come with HTTP 200.
On this page
https://api.solvecha.com/The poll request of the first NopeCHA API. It returns the answer of a job that you created on the root path or on a /v1/recognition/... path. Errors are answered with HTTP status 200: while the job is not ready you get {"error": 14, "message": "Incomplete job"}.
#Authorization
Send your API key as Authorization: Bearer YOUR_API_KEY. Other ways are the key field of the body and the key query parameter. See Authentication.
#Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
string | required | The job id. |
key |
string | optional | Your API key, if you do not send it in the Authorization header. |
#Response
#200 OK
The job is ready.
#Errors
HTTP status 200 with an error body, as in the response examples:
| Code | HTTP status | When |
|---|---|---|
14 Incomplete job |
200 | The job is not ready yet. Poll again in one second. |
10 Invalid request |
200 | The id is missing or unknown. |
11 Rate limit reached |
200 | Your key is above the poll requests per minute of its plan. |
15 Invalid key |
200 | The key is missing, malformed or unknown. |
9 Unknown error |
200 | Server error. Retry after a few seconds. |
All codes are on the Errors page.
Solvecha is an independent service. It is not affiliated with NopeCHA, 2Captcha, CapSolver, Google or CloakHQ. Their names describe compatibility or recommendations only. Figures come from our own tests, see the compare page.