Legacy paths
Get the status of your key (legacy path)
NopeCHA's original status path: GET /status. Errors come with HTTP 200.
On this page
GET
https://api.solvecha.com/statusSame answer as Get the status of your key, on the path of the first NopeCHA API. Errors are answered with HTTP status 200.
#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 |
|---|---|---|---|
key |
string | optional | Your API key, if you do not send it in the Authorization header. |
#Response
#200 OK
The state of your key.
#Errors
HTTP status 200 with an error body, as in the response examples:
| Code | HTTP status | When |
|---|---|---|
11 Rate limit reached |
200 | More than 600 status requests per minute. |
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.