← nocaptchaai.comDocs
    DocsChangelog

    Get Started

    Start Here
    QuickstartAuthenticationError Codes
    Browser Extension

    Captcha Types

    Token Tasks
    Cloudflare Turnstile Task
    Image Tasks
    ReCaptcha v2GeeTest V4ImageToTextBLS CaptchaBinanceAWS WAFTikTokDB-betMTCaptchaTencentProSOPO

    API Reference

    Overview
    Solver
    Create async captcha solving taskPoll task result (GET)Poll task resultSolve captchaGet response statusCollect endpoint (reserved)Report accuracy feedbackGet accuracy report
    Balance
    Check balance & plan infoLegacy balance formatList all error codes
    System
    Health check

    SDKs

    OverviewPythonJavaScript / Node.jsGo

    Agents

    OverviewModel Context Protocol (MCP)Claude CodeOpenAI CodexCursorClineOpenClaw

    Guides

    Browser ExtensionError HandlingChoosing a Task Type
    ← nocaptchaai.com
    Get API key
    Sign inGet API key

    Authentication

    How to authenticate requests to the NoCaptchaAI API.

    Loading…

    PreviousQuickstartNextError Codes
    [ ] Docs[ ] Extension[ ] Pricing[ ] Changelog[ ] Partners[ ] Terms[ ] Privacy[ ] Cookies[ ] Refunds[ ] Contact

    Spicrawl

    Free web scraping API for AI agents.

    spicrawl.com

    Spicrawl

    © 2026 NoCaptchaAI

    Every request to the NoCaptchaAI API must be authenticated with your API key. This page covers where to find your key and the two ways to send it.

    Get an API key

    Sign in to the NoCaptchaAI dashboard and copy your API key from the account page. The same key works across the async (/createTask), sync (/solve), and /balance endpoints.

    The API base URL is:

    text
    https://api.nocaptchaai.com
    

    Treat your API key like a password. Never embed it in client-side code, browser extensions, mobile apps, or public repositories. Always call the API from a server you control, and rotate the key immediately if it leaks.

    Authentication methods

    There are two methods, depending on the endpoint you call.

    MethodWhere the key goesEndpoints
    clientKeyJSON request bodyPOST /createTask, POST /getTaskResult
    apikeyRequest headerPOST /solve

    Method 1 — clientKey in the JSON body

    The async flow passes the key as a clientKey field inside the request body.

    bash
    curl -X POST https://api.nocaptchaai.com/createTask \
      -H "Content-Type: application/json" \
      -d '{
        "clientKey": "YOUR_API_KEY",
        "task": {
          "type": "ImageToTextTask",
          "body": "BASE64_IMAGE"
        }
      }'
    

    The same clientKey is required when you poll for the result:

    bash
    curl -X POST https://api.nocaptchaai.com/getTaskResult \
      -H "Content-Type: application/json" \
      -d '{ "clientKey": "YOUR_API_KEY", "taskId": "TASK_ID" }'
    

    Method 2 — apikey request header

    The synchronous /solve endpoint reads the key from an apikey header instead of the body.

    bash
    curl -X POST https://api.nocaptchaai.com/solve \
      -H "apikey: YOUR_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "type": "ImageToTextTask",
        "body": "BASE64_IMAGE"
      }'
    

    Check your balance

    You can verify a key and see remaining credits with the /balance endpoint, which takes the key as the apiKey query parameter:

    bash
    curl "https://api.nocaptchaai.com/balance?apiKey=YOUR_API_KEY"
    

    A KEY_DOES_NOT_EXIST error (code 1) means the key is missing or malformed. See Error Handling for the full list of error codes.