Introduction
Automation scripts, scrapers, and end-to-end test suites regularly run into hCaptcha widgets. When a solving service quietly removes support, those workflows break without warning. In early 2025, two widely used providers stopped documenting hCaptcha integrations, leaving many developers searching for a replacement. This post explains how token-based solving works, when you can avoid a third-party service entirely, and how to connect your existing code to a new API.
What Happened
Around the start of 2025, 2Captcha removed hCaptcha from its public API documentation. Shortly after, CapSolver's hCaptcha documentation page began returning a 404 error. If your scraper or test suite was built to send hCaptcha jobs to either service, those integrations no longer work as expected. You need a different endpoint to submit sitekeys and receive valid tokens.
One replacement option is a dedicated hCaptcha solving API that accepts a sitekey and page URL, then returns a token. The request stays open for up to 90 seconds while the solve completes. If the time limit expires before a result is ready, the API returns a 202 response with no token, and you can poll a status endpoint until the solve finishes, fails, or expires. Failed attempts are not billed.
Why This Matters
Sites you control
If the hCaptcha widget appears on an application you own, you probably do not need a solving service at all. hCaptcha provides test keys specifically for development and continuous integration. By configuring your test environment with the published test sitekey and matching secret, the widget passes without presenting a challenge, and your backend accepts the dummy token through the standard siteverify endpoint.
Sites you do not control
For scrapers collecting public data, monitoring jobs, or tests running against third-party staging environments, a solving service is still required. These workflows depend on obtaining a valid hCaptcha token and submitting it exactly as a real browser would.
Key Takeaways
- Token lifecycle: A solved hCaptcha token starts with P1 underscore, works only once, and expires after about two minutes. Request it immediately before you submit.
- Browser identity: Some sites check that the browser sending the token matches the one that solved the challenge. Send the User-Agent string provided by the solver with your request.
- Integration points: Read the sitekey from the data-sitekey attribute or the widget iframe URL, send it with the target page URL to the solver API, then place the returned token in the h-captcha-response field or pass it to the page's JavaScript callback.
- Feedback loop: If a token passes hCaptcha but the target site still rejects the submission, report the solve ID to the feedback endpoint so the provider can adjust.
- Legacy compatibility: If your code already targets 2Captcha or CapSolver, compatibility endpoints let you keep most of your existing client logic while pointing to a new base URL.
Conclusion
hCaptcha is not unsolvable, but the ecosystem around it has shifted. Developers maintaining scrapers, monitoring tools, or automated test suites should verify which services still support hCaptcha, use test keys for their own applications where possible, and prepare to route solving jobs through a current API. Full integration references and language-specific examples are available from the provider's documentation portal.

Discussion
Join the conversation
Thoughtful reactions, questions, and follow-up ideas help shape the next story.