Errors

Errors return a stable error code and a requestId. Quote the request ID in a support message; it identifies the failure without exposing your input.

{
  "error": "insufficient_funds",
  "requestId": "6c1e0b2a-4d3f-4a7e-9b8c-1f2e3d4c5b6a"
}

HTTP	`error`	Meaning	Reserved?
400	`invalid_json`, `invalid_email`, `invalid_domain`, `invalid_name`, `unexpected_fields`	The body could not be used.	no
401	`valid_api_key_required`, `invalid_or_revoked_key`	Missing, revoked or unknown key.	no
402	`insufficient_funds`	Not enough available credit to reserve the job.	no
403	`key_scope_denied`	The key is not scoped for this operation.	no
403	`verified_email_required`, `account_frozen`, `payment_reconciliation_hold`	The account cannot submit work right now.	no
404	`job_not_found`	No job with that ID on this account.	—
409	`idempotency_conflict`	The same idempotency key was reused with a different input.	no
429	`rate_limit_exceeded`, `job_capacity_limit`	Too many submissions or jobs in flight. Retry after `Retry-After` seconds.	no
503	`engine_disabled`, `new_jobs_maintenance`, `engine_temporarily_unavailable`	Execution is paused or unreachable.	no

Retrying

Retry 429 and 503 after the interval in Retry-After (or a few seconds when absent), reusing the same Idempotency-Key. You will get the original job if it was admitted, or a fresh admission if it was not.
Do not retry 400, 402, 403 or 409 unchanged; fix the request first.
A verify result with retryable: true is a different thing: the job completed, and the host asked us to try again later. Submit a new job in a few hours.

Get started

Concepts

Reference

Retrying

​Retrying

Retrying