Error Codes & Troubleshooting

When an API call fails, first locate the category by HTTP status code, then follow the fix. The error response body is JSON; error.message carries the specific reason.

Error Code Cheat Sheet

HTTP statusMeaningCommon causesFix
400 Bad RequestMalformed requestInvalid JSON, missing model / messages, wrong field typesCheck the request body with a JSON validator; fix fields against the tables in API Calls
401 UnauthorizedToken invalid or missingNo Authorization header, mistyped token / stray spaces or newlines, token deletedCheck the header format Authorization: Bearer sk-your-token; confirm the token exists on the API Keys page and copy the full value
403 ForbiddenNo permissionToken disabled, token has a model scope or IP allowlist, account bannedOn the API Keys page enable the token and check the model restriction and IP allowlist under "Advanced Settings"; otherwise see Contact Us
404 Not FoundModel or path doesn't existMisspelled model name, wrong case, model not in your groupCopy the exact model name from Model Plaza; confirm the API path is correct (see Base URLs & Auth)
429 Too Many RequestsRate limit hitToo many requests in a short window, exceeding RPM / TPM limitsLower the request rate and retry with exponential backoff; if it persists, report via Contact Us
5xx Server ErrorServer-side errorUpstream fluctuation or internal gateway errorRetry after 1–2 minutes; if it keeps happening, report to us (contacts in Contact Us)

Platform-Specific Errors

Error messageMeaningFix
insufficient quotaAccount balance is 0Top up on the top-up platform and retry
token quota used upThe token's own cap is used up (account balance is still fine)On the API Keys page, edit the token to raise its quota or enable unlimited quota
token expiredThe token has passed its expiryEdit the token to extend its validity, or create a new one
no available channelNo available route for this model right nowRetry later; if unavailable for long, report via Contact Us
NOTE

"Sufficient balance but still insufficient quota" is 90% of the time a token-level limit (quota, expiry), not the account balance — they are different things. Troubleshooting order: account balance (Wallet) → token quota and expiry (API Keys) → token model scope.

Three Universal Checks

For any error, run through these three first — they resolve most problems:

  1. Is the URL right? base_url is https://api-model.shuntianchuang.cn/v1; full endpoints in Base URLs & Auth.
  2. Is the key right? The token is complete with no stray whitespace and is enabled — see API Key Management.
  3. Is the model name right? Copy it from Model Plaza and mind the case (this site has distinct models like qwen-plus and Qwen-plus).

If the problem survives all three, report it via the contacts in Contact Us, attaching: the time, model name, status code, and the error.message content (remember to redact your token).