• English

    • Error Codes

    Every status code the service returns, with scenarios and handling. To locate by symptom first, see Troubleshooting.

    Authentication (401)

    ScenarioDescriptionHandling
    Missing keyNo auth header on the requestCheck key injection in your client; auth methods in API Endpoints
    Invalid keyKey does not exist or is malformedRe-copy from the API Keys page, watch for stray spaces
    Disabled keyManually disabled, or a team key disabled by the ownerConfirm status on the keys page; contact the owner for locked team keys
    Expired keyThe expiry set at creation has passedCreate a new key

    Quota and rate limits (402 / 429)

    ScenarioDescriptionHandling
    Insufficient balanceSubscriptions and balance both exhaustedTop up or renew on the purchase page
    Key quota exhaustedThe key's own spending cap is reachedRaise the cap or create a new key
    Team limit exceededA member hit a daily/weekly/monthly limitWait for the cycle reset or ask the owner to adjust on the team page
    Concurrency exceeded (429)Too many simultaneous requestsReduce concurrency, queue retries
    Rate limited (429)Requests too dense in a short windowRetry with exponential backoff

    Permissions (403)

    ScenarioDescriptionHandling
    Model not in groupThe requested model is not in the key's groupCheck the group's model list in the model plaza
    Format mismatchThe group does not accept this protocol formatSwitch to the matching-format group, see Core Concepts
    Client-restricted groupThe group only allows specific clientsChange client or group — read the group labels
    Capability not enabledThe group does not offer this capability (e.g. image generation)Use a group that supports it
    Account state issueA team-related account is disabled or the team suspendedConfirm on the team page

    Requests (400 / 404)

    ScenarioDescriptionHandling
    Composite prefix missingModel ID has no prefixWrite prefix/modelID, see Composite Keys
    Composite prefix invalidPrefix not in the mapping or malformedVerify the mapping on the keys page
    Interface unsupported for composite keysRealtime-style interfaces do not support composite keysUse a regular key
    Malformed request bodyInvalid JSON, missing required fieldsFix against the client or SDK docs
    Endpoint not found (404)Wrong path, extra or missing /v1Check API Endpoints
    Model not found (404)Misspelt model IDFetch the model list and use the exact returned ID

    Upstream (5xx / 529)

    ScenarioDescriptionHandling
    Upstream overloaded (529)Vendor-side capacity is tightRetry later; the system cools the affected upstream account automatically
    Upstream timeoutLong reasoning responds slowlyRaise your client timeout
    Transient upstream errors (502/503)Vendor-side flakinessThe service fails over automatically; report if consistently reproducible
    Internal error (500)Service faultSubmit the report template with the request ID

    Reading error responses

    • The message field usually states exactly what is missing or wrong — read it fully before digging;
    • The request ID in the response headers is the only handle for locating a single request — always include it in reports;
    • Some clients swallow response bodies and show only the status code; replay with curl -i to get the full picture.
    © 2026 ByteSeek Limited. All rights reserved.TermsPrivacyDisclaimer