SDKs & API Versioning

Official client libraries are on the roadmap. Today the REST API and 2Captcha-compatible clients cover every use case.

Official SDKs — Roadmap

We do not ship official SDKs yet; they are planned and will be announced on the API changelog. The REST API is intentionally small — one POST per solve — so direct HTTP integration takes minutes in any language:

Using 2Captcha-Compatible Libraries Today

For xCaptcha workloads, any existing 2Captcha client library works out of the box — CaptchaKings implements the same in.php/res.php contract (OK|... responses, json=1 support, matching error strings):

python

# pip install 2captcha-python
from twocaptcha import TwoCaptcha

solver = TwoCaptcha('YOUR_CAPTCHAKINGS_KEY', server='captchakings.com')
result = solver.normal('captcha.png')   # routed to the xCaptcha pipeline
print(result['code'])

Compatibility clients cover xCaptcha only. For OCR, Tencent, GeeTest, MTCaptcha, or Amazon WAF, call the native endpoints directly — see the migration guide.

API Versioning Policy

Current version: v1 (unversioned paths — /api/*.php, /in.php, /res.php).
Stability: existing request/response fields will not be removed or renamed in v1. New fields may be added; clients should ignore unknown JSON keys.
Breaking changes: would ship under a versioned path (e.g. /api/v2/) and be announced on the changelog before launch, with v1 kept online during migration.

Browser Extension (No Code)

If you don't want to integrate at all, the CaptchaKings Solver Chrome extension solves supported captchas directly in your browser using the same account balance.