Gengxi API Developer Docs
Troubleshooting
Diagnose authentication, model, quota, upstream, and streaming failures.
Recommended diagnostic order
- Check the API key and authorization header.
- Call GET /v1/models with the same key.
- Check /usage for balance and quota.
- Retry safely with exponential backoff when appropriate.
- Contact Support with the Request ID if the issue persists.
Common failures
| Symptom | Check |
|---|---|
| 401 | Missing, invalid, disabled key, or inactive user |
| 403 | Expired key, insufficient balance, or denied access |
| 404 model | Model identifier and current key/group model list |
| 429 | Retry-After, quota, rate, and rolling limits |
| 500 | Request ID and safe retry |
| 502 / 503 | Temporary upstream or capacity issue; retry later |
| Streaming interruption | SSE parsing, network timeout, cancellation, and terminal events |
Streaming checks
- Confirm Content-Type is text/event-stream.
- Parse complete SSE frames.
- Handle response.failed for Responses.
- Do not require [DONE] for Responses streams.
- Retry only when repeating the request is safe.
Contact Support
When contacting Support, include the Request ID, approximate time, endpoint, status code, and a redacted request summary. Never send your full API key.
Contact Support →