Skip to main content

Errors

Error response structure and handling guidance for the Managed Agents API.

When a call fails, the service returns the following error structure, where request_id matches the x-request-id response header:
{
  "type": "error",
  "error": {
    "code": "AGENT_001",
    "message": "Agent not found"
  },
  "request_id": "35feaacc-7914-948f-a38e-010bf8095bc1"
}

Common error codes

codeHTTP statusDescription
AGENT_001404Agent not found
400400Parameter validation failed; message gives the reason (for example, limit must be between 1 and 100)
InvalidApiKey401API Key missing or invalid (gateway layer)
Endpoint.AccessDenied403Workspace does not exist or is not accessible (gateway layer)
BadRequest.IllegalEndpoint400Workspace route is invalid (gateway layer)
Authentication and workspace-routing errors are returned directly by the gateway in a flat {"request_id", "code", "message"} structure; business errors are returned by the service, with the error code in error.code.

Common HTTP status codes

HTTP statusDescription
400Missing parameter, malformed format, or value out of range
401Invalid API Key
403No access to the workspace
404Resource not found
409The current resource state does not allow this operation
429Too many requests
500Internal service error
When troubleshooting, use request_id to locate the specific request. Continue with the endpoint list in the Overview.
Managed Agent API
Flow Agent API
Sandbox API
RAG API
Long-term Memory
ParseX API
Security API
Framework Integration