Jev API Error Codes

Gateway status codes

The table describes responses produced by the current Best Jev AI /v1/systemone gateway. A provider failure is surfaced as 502; provider-native status codes are not passed through as gateway statuses.

• 400 — invalid JSON, a missing model or questions object, no questions, more than eight questions, or an unsupported question type. Fix the request before retrying.
• 401 — missing or invalid API key, or no signed-in session for the Playground. Check Bearer formatting and key status.
• 402 — the API account has insufficient credits. Add credits or use an account with a valid balance.
• 413 — serialized request body exceeds 32 KiB. Remove irrelevant state or reduce the number and size of fields.
• 502 — the provider rejected the request, returned unusable output, omitted usage, or could not be reached. Review the request, then retry cautiously if the operation is safe.
• 503 — the decision provider is not configured for this deployment. Contact the site operator.

Retry only transient failures

Do not retry 400, 401, 402, or 413 unchanged: the same request will fail again. For a transient 502, use a bounded exponential backoff with jitter and a small retry budget. This POST endpoint does not expose an idempotency key, so make sure repeated evaluations are safe for your workflow.

• Set a request timeout and cap the number of attempts.
• Keep a human-review path for high-impact or uncertain decisions.
• Log the status and a safe error summary; never log API keys or unnecessary personal data.

The signed-in Playground browser session, when calling without a Bearer API key, is limited to one request every three seconds. This is not a documented API-key endpoint rate limit.