Skip to content
EASYJEV

Errors & Status Codes

Every status code EasyJev returns: the unified error JSON shape with request_id, the full code table (400/401/402/403/404/413/422/429/502), retry guidance and upstream pass-through semantics.

The unified error shape

Gateway-originated failures (auth, quota, rate limit, upstream exhaustion…) all return this JSON envelope on /v1/* paths. Upstream validation errors are the exception — they pass through unchanged (see the systemone page).

JSON · error envelope
{
  "error": {
    "message": "Balance is not enough to make this call",
    "type": "insufficient_quota",
    "code": "insufficient_quota"
  },
  "request_id": "8f14e45fceea167a5a36dedd4bea2543"
}

Status codes

HTTPtypecodeMeaning / what to do
400invalid_request_errorupstream pass-throughUpstream rejected the request body. Read the upstream message; not billed.
401authentication_errorinvalid_api_keyMissing/wrong Bearer key. Check the sk- value; a disabled key also lands here.
402insufficient_quotainsufficient_quotaBalance is zero/negative. Top up, then retry.
403authentication_erroraccount_suspended / key_disabledAccount or key disabled — contact support.
404invalid_request_errormodel_not_foundModel not on sale (or typo). List valid names via GET /v1/models.
413invalid_request_errorpayload_too_large / media_too_largeRequest over size limits — shrink the body or split the asset.
422invalid_request_errorbad_request (gateway) / upstream pass-throughMissing model/state/questions, or upstream schema rejection.
429rate_limit_errorrate_limit_exceededPer-key RPM/TPM hit. Back off (the limit resets inside a minute) and retry.
502api_errorupstream_failedAll channel+key attempts failed after failover. Safe to retry with backoff; contact support with request_id if it persists.

Retry guidance

RETRY

Retry safely on 429 (after backing off — the sliding window frees capacity within a minute) and 502 (failover was exhausted; transient upstream issues are common). Do not blind-retry 400/401/402/403/404/413/422 — the request itself must change first. Every retry carries a fresh request_id, so reconciliation stays clean.