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.

Errors you should correct first

400 indicates invalid input, 401 missing or invalid authentication, and 403 an origin or account restriction. 413 rejects an oversized body; 415 requires JSON. Changing retries will not fix these conditions.

402 means insufficient credits or inactive API access. Inspect the account 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.

Try a decision ↗

Continue your workflow

API docs

Jev API documentation

The Jev API Pro endpoint accepts a bounded classification task and returns one allowed label. Use a server-side API key from an account with active API access.

Read the guide ↗
Ask about plans & usage

Find a product answer

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

Contact

Take the next decision into your workspace.

3 anonymous attempts 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.