Troubleshooting
Find the cause of authentication, request and connection errors.
Read the error body as well as the HTTP status. Start with the smallest request and check the same key, model and endpoint used by your application.
| Symptom | What to check |
|---|---|
| 401 · Authentication | Check that the API key is complete, enabled and unexpired. Confirm the client is sending the Zashmodel key to the Zashmodel base URL. |
| 403 · Access denied | Check account status, key restrictions, allowed IPs and model group permissions. Use the error message to identify the denied permission. |
| 404 · Model or endpoint | Check the exact model ID and request path. Remove duplicate /v1 segments. endpoint_not_enabled means this endpoint is not enabled on the site. |
| 400 · Request parameters | Start with a minimal example. Check the model protocol, required fields, context length and support for tools, images or other optional parameters. |
| 429 · Rate or concurrency limit | Reduce parallel requests and retry with increasing delays. If Retry-After is present, respect it. Repeated immediate retries increase the load. |
| Insufficient balance or key quota | Check both the wallet balance and the API key quota. Increasing a key quota does not add funds to your account. |
| 5xx, timeout or interrupted stream | Check request logs before retrying: a timeout does not prove the request was never processed. Use bounded retries and contact support if the problem continues. |
Still need help?
Include the request ID if available, time and timezone, model ID, endpoint, HTTP status and a redacted error message. Never send your API key, account password or payment credentials.
Contact support →