Skip to content

Developer portal

Errors & status codes

Every failure path should be actionable for operators and engineers.

Error envelope

Typical error body

{
  "status": "error",
  "message": "Invalid API key. Check the pilot token and try again.",
  "detail": "optional string or validation object"
}

HTTP status codes

CodeMeaningTypical causeSuggested fix
400Bad requestMalformed JSON or missing required headers.Validate Content-Type and JSON syntax before retrying.
401UnauthorizedMissing or invalid API key in Authorization or x-api-key header.Send Bearer <key> or x-api-key with a valid pilot token.
422Unprocessable entityInvalid payload shape, unsupported problem type, or infeasible constraints.Fix field errors in the response detail; relax constraints and retry.
429Too many requestsPer-key rate limit exceeded (default 120 requests per minute).Backoff with jitter; cache results; request a higher limit for production.
500Internal server errorUnexpected backend failure.Retry with exponential backoff; contact support if persistent.
501Not implementedProblem type not yet supported on the live solver path (routing, allocation).Use type schedule for live jobs, or follow the roadmap for routing/allocation.

Retry guidance