Quickstart
Quick Troubleshooting
Diagnose authentication, balance, model, rate-limit, network, and response-parsing issues by status and symptom.
Record the HTTP status, error object, request time, and request ID first, then work through the checks below.
One-minute diagnosis
| Symptom | Check first | Action |
|---|---|---|
401 | Key, Bearer format, environment variables | Reload environment variables and check for extra quotes or spaces in headers. |
402 | Account balance | Review usage and top up; confirm the key belongs to the intended account. |
404 | URL and model identifier | Confirm the path is /v1/chat/completions and copy the model ID from the catalog. |
429 | Concurrency, rate limits, quota | Add a queue and exponential backoff; request a higher quota if necessary. |
5xx | Platform or upstream node | Retry safe requests a limited number of times; retain the request ID for support. |
| Connection failure | DNS, proxy, TLS, outbound network | Use cURL from the same environment to check access to the Base URL. |
| Empty output | finish_reason, stream handling | Read delta.content for streaming requests and check tool-call results. |
Minimal reproduction
Remove business frameworks, proxy layers, and complex parameters, leaving only a minimal cURL request. If that succeeds, check SDK configuration, application middleware, and network proxies.
curl -i https://api.apiqik.com/v1/chat/completions \
-H "Authorization: Bearer $APIQIK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"qwen-turbo","messages":[{"role":"user","content":"ping"}]}'Information for support
- Request time and time zone.
- Endpoint, model identifier, HTTP status, and request ID.
- A redacted minimal request body and the complete error object.
- Whether the issue is reproducible and affects both streaming and non-streaming requests.
- Runtime environment, SDK language, and version. Do not include the complete API key.