DOCS

Jev API error handling

Every API error includes a code, a readable message, and a request identifier. Use these fields to distinguish a request you can correct from a temporary service failure.

Your application sends a bounded request; Jev returns a typed answer; your policy controls the next action.
Your application sends a bounded request; Jev returns a typed answer; your policy controls the next action.

Errors you should correct first

400 indicates invalid input, 401 missing or invalid authentication, and 403 an origin or account restriction. An expired API access period makes its key invalid for decisions and returns 401. 413 rejects an oversized body; 415 requires JSON. Changing retries will not fix these conditions.

402 means insufficient credits, or an inactive plan when creating an API key. Inspect the account and endpoint before submitting more work.

Conflicts and temporary failures

409 can indicate a request still running, a reused key with different content, or a previously failed request. Reuse the same key only to retrieve the same logical request. 429 means a rate limit.

502 or 503 can indicate an invalid provider response, timeout, unavailable configuration, or provider outage. We do not silently switch to another model. Failed account decisions are refunded.

A bounded recovery policy

For an uncertain connection, wait briefly and retry the same logical request at most twice with the same idempotency key. Stop and surface the error if it persists. Include the request identifier when contacting support; do not send API keys or private customer text.

Request contract · Request limits and credit rules

Try a decision ↗

Continue your workflow

Ask about plans & usage

Find a product answer

Answers come from the published product guide. For account-specific questions, contact support.

Contact
DAILY BONUS

2 free credits, every day

Claim 2 free credits each UTC day — 14 across seven claims. No purchase needed. Credits do not expire.

    Resets at 00:00 UTC. No streak required.

    Try a decision →

    Take the next decision into your workspace.

    1 anonymous attempt per day · 20 signup credits · No card for the trial

    Sign in ↗

    Tell us what you need

    Describe the workflow you want to classify, the volume you expect, and the outcome you need. We reply by email.

    10–2,000 characters. Never include passwords, API keys, or payment details.