Errors

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

Status

When

401

Missing, invalid, or inactive API key.

402

Insufficient funds to reserve the job’s price.

403

API key lacks permission for the requested model.

404

GET /jobs/{job_id} for an unknown id or a job owned by another account.

422

Validation failure — unfetchable URL or oversized input.

502

Upstream storage failure while ingesting inputs.

503

The project or the requested model is paused — try again later.

Handling tips

401 — Authentication

Verify the Authorization: Bearer <key> header and that the key is active. See Authentication.

402 — Insufficient funds

Check GET /balance. The available amount must cover the job’s reserved price.

403 — Model permission

The key isn’t scoped for the requested model. Grant access in the web panel or use a different key.

422 — Validation

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.

503 — Paused

Transient — the project or model is paused. Retry later, ideally with the same Idempotency-Key.

Handling tips