Skip to main content

Errors

AXTL returns structured API errors for most domain failures. Some authentication middleware failures still return a simpler string error, so clients should not assume every 401 has a code.

Error shape

{
  "error": {
    "code": "agent_not_found",
    "message": "Agent not found",
    "details": {}
  }
}
details may be omitted.

Common status codes

StatusMeaning
400Invalid request.
401Missing or invalid authentication.
403Authenticated but not allowed.
404Resource not found.
409Current resource state does not allow the action.
413Request body too large.
415Unsupported content type.
422Validation failed.
429Quota or rate limit exceeded.
500Internal error.
503Service unavailable or required configuration missing.

Common error codes

CodeUsually means
agent_not_foundThe agent does not exist or is not owned by the caller.
agent_not_readyThe backend is not ready for deployment.
deploy_in_progressA deployment is already running.
endpoint_not_availableNo endpoint URL is available yet.
quota_exceededA quota has been reached. Limits may vary by workspace during the beta.
missing_agent_api_keyPublic invocation did not include an agent API key.
malformed_agent_api_keyPublic invocation did not use a bearer agent API key.
invalid_agent_api_keyPublic invocation used an unknown key.
agent_api_key_revokedPublic invocation used a revoked key.
agent_api_key_scope_mismatchPublic invocation used a key for another agent.
not_deployedThe agent has no live endpoint yet.
invalid_jsonThe request body was not valid JSON.
endpoint_timeoutThe deployed backend did not respond before timeout.
endpoint_unreachableAXTL could not reach the deployed backend.