Choosing a Task Type
Pick the right NoCaptchaAI task type for your captcha.
NoCaptchaAI exposes one task type per captcha. Picking the correct type is the most important decision when you integrate — it determines what you send and what you get back. The types fall into two families:
- Token tasks return a verification token that you submit to the target site, exactly as a real user's browser would (for example Turnstile, reCAPTCHA, and GeeTest v4).
- Image / recognition tasks return the answer itself — coordinates to click, the recognized text, or a grid selection — which you then apply in your own automation (for example reCAPTCHA image challenges, BLS, OCR, Binance, AWS WAF, and TikTok).
Captcha to task type
| Captcha | Task type | Docs |
|---|---|---|
| Cloudflare Turnstile | AntiTurnstileTask | /docs/token/turnstile |
| Cloudflare (challenge) | token task | /docs/token/cloudflare |
| GeeTest v4 (token) | token task | /docs/token/geetestv4 |
| MTCaptcha (token) | token task | /docs/token/mtcaptcha |
| reCAPTCHA v2 (images) | image task | /docs/imagetasks/recaptcha |
| GeeTest v3 | image task | /docs/imagetasks/geetestv3 |
| GeeTest v4 (image) | image task | /docs/imagetasks/geetestv4 |
| ImageToText / OCR | image task | /docs/imagetasks/imagetotext |
| BLS | image task | /docs/imagetasks/bls |
| Binance | image task | /docs/imagetasks/binance |
| AWS WAF | image task | /docs/imagetasks/awswaf |
| TikTok | image task | /docs/imagetasks/tiktok |
Each linked page lists the exact type value and the fields that task requires. When in doubt, start from the captcha you're facing and follow its link.
Async vs sync
All tasks are sent to https://api.nocaptchaai.com with your dashboard API key. There are two ways to run them:
- Async (recommended): submit with
/createTask, then poll/getTaskResultuntil the result is ready. This scales well, handles longer-running challenges, and is the right default for production workloads. - Sync: call
/solveand wait for the answer in a single request. It's simpler for quick tests and low-volume use, but ties up the connection until the solve finishes.
See the Quickstart for a working end-to-end example, and the API Reference for the full request and response schemas.