Skip to main content
The API uses conventional HTTP status codes to signal success and failure.
StatusWhen
401Missing, invalid, or inactive API key.
402Insufficient funds to reserve the job’s price.
403API key lacks permission for the requested model.
404GET /jobs/{job_id} for an unknown id or a job owned by another account.
422Validation failure — unfetchable URL or oversized input.
502Upstream storage failure while ingesting inputs.
503The project or the requested model is paused — try again later.

Handling tips

Verify the Authorization: Bearer <key> header and that the key is active. See Authentication.
Check GET /balance. The available amount must cover the job’s reserved price.
The key isn’t scoped for the requested model. Grant access in the web panel or use a different key.
Common causes: an input_images_urls entry that can’t be fetched, total input size over 40 MB, or an aspect_ratio the model doesn’t support.
Transient — the project or model is paused. Retry later, ideally with the same Idempotency-Key.