Skip to main content

What does an error look like?

Every error uses the same envelope, described in the API introduction. The HTTP status tells you the category, code is a stable string safe to branch on, and details — when present — carries the numbers you need to act (a limit, a retry delay, the missing scope).
message is for humans and can change; never branch your code on it. For deploy and runtime problems that don’t come from the API itself (crash loops, missing dependencies, OOMKilled), see Common Errors — this page only covers the stable code values the API answers with.
VALIDATION_ERROR (400) covers request-shape problems across every route — a required field missing, the wrong type, an out-of-range value. details.path names the offending field, e.g. "memory" or "user.name".

Auth & API keys

Plans & billing

Applications

Deploy & GitHub

Files

Network & domains

Databases

Environment variables

Snapshots

Workspaces

Rate limits & quotas

See rate limits for the full breakdown of budgets per plan.

General

This catalog lists every code from the public API contract. A route can still answer other standard HTTP errors (like a generic 404 for an unknown path) that don’t carry one of these code values.