Troubleshooting
Start with your application’s error, request time, requested model, and Divyam base URL. Keep the API key out of screenshots, logs, and reports you share.
Authentication errors
For HTTP 401, check that your application uses the complete Divyam API key. Do not use the email verification code, inventory display hint, or browser session token. Check whether the key was revoked and whether the application loaded the latest secret.
If the secret is lost, follow API key replacement and rotation. For console sign-in failures, check your email address and request a fresh verification code.
Credit exhaustion
For HTTP 402, open Credits & Billing and check your remaining credit. Resolve the credit restriction before retrying. Repeated requests do not replenish credit. Credit purchases are not available in the current console release.
Connection and model errors
| Symptom | What to check |
|---|---|
| HTTP 403 | Check account access and whether the plan permits the requested model. |
| Model not found | Copy an available ID from Models & Pricing, including its complete prefix. |
| HTTP 404 for the route | Use the base URL in an SDK. Use the full completion URL for a direct HTTP request. |
| HTTP 429 | Reduce request volume and retry after the reported delay. |
| HTTP 502 or 503 | Check the error message. Retry later if the upstream service or model is unavailable. |
| The application uses an old connection | Check configuration overrides and restart or reload when required. |
For this hosted console, the example base URL is https://api.demo.divyam.ai/v1.
The direct completion URL is https://api.demo.divyam.ai/v1/chat/completions.
Use the base URL supplied by your account if it differs.
Missing logs or usage
- Confirm the application received an answer or an error from the configured Divyam endpoint.
- Sign into the account that created its key.
- In Logs, select all models and a period covering the test. Leave Status at All statuses.
- Compare timestamps in UTC and load older requests if necessary.
- Refresh after reporting has caught up. Usage can lag behind individual requests.
- Check your application’s provider selection and configuration overrides if records remain missing.
Console reporting may not contain every request rejected before inference begins. Keep the original application error when investigating authentication or routing failures.
Report an unresolved problem
Share the request time with timezone, requested model, HTTP status, and redacted error with your Divyam administrator. Include a request ID when the error or console provides one. Describe the application and the operation that failed.