Application Process
To use hCaptcha Protocol Recognition API, first open the Ace Data Cloud Console and copy your API Token. If you are not logged in, you will be redirected to sign in and brought back to this page automatically. A single API Token works across every service on the platform — no need to subscribe per service. New accounts receive free starter credit; when it runs low you can top up your shared balance in the console.📘 Full documentation: hCaptcha Protocol Recognition API →
Basic Usage
First, understand the basic usage method, which is to input the URL of the website that needs to process the hCaptcha verification code to obtain the processed result. You need to simply pass awebsite_url field. Our example website is: https://accounts.hcaptcha.com/demo. We need to obtain the website_key from the website_url page. First, open this webpage, press F12 to enter the console, and then perform a global search for hcaptcha-demo in the Elements page. We can get the following result:
The string corresponding to data-sitekey is the value of the website_key. Below are the specific parameter results:
Here we can see that we have set the Request Headers, including:
accept: the format of the response result you want to receive, filled in asapplication/json, which is in JSON format.authorization: the key for calling the API, which can be selected directly after application.
website_url: the URL of the website that needs to process the verification code.website_key: the website key identifier in hCaptcha.
- First, manually go through the verification, as shown in the figure below:
- Then click submit and watch the changes in the console’s network, as shown in the figure below:
- Analyze the construction of this submitted POST request, and finally right-click on the request to copy the CURL code, as shown in the figure below:
https://accounts.hcaptcha.com/demo, and we only need to submit the parameters g-recaptcha-response, h-captcha-response, and email. Then we just need to pass the processed token into the data below, and the corresponding CURL code for calling the token verification is as follows:
Error Handling
When calling the API, if an error occurs, the API will return the corresponding error code and message. For example:400 token_mismatched: Bad request, possibly due to missing or invalid parameters.400 api_not_implemented: Bad request, possibly due to missing or invalid parameters.401 invalid_token: Unauthorized, invalid or missing authorization token.429 too_many_requests: Too many requests, you have exceeded the rate limit.500 api_error: Internal server error, something went wrong on the server.

