HTTP status codes
Common error payloads
WebSocket errors
WebSocket protocol errors are sent as message typeerror:
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Common HTTP and WebSocket errors returned by the platform API.
| Status | Meaning | Typical cause |
|---|---|---|
| 200 | Success | Request completed successfully. |
| 201 | Created | Resource created (example: tenant or intent). |
| 400 | Bad Request | Validation error or business rule failure. |
| 401 | Unauthorized | Missing/invalid/expired auth token. |
| 403 | Forbidden | Authenticated but not linked to tenant. |
| 404 | Not Found | Resource does not exist in tenant scope. |
| 500 | Internal Server Error | Unexpected processing or escalation failure. |
{ "error": "Missing or invalid authorization header" }
{ "error": "Conversation not found" }
{ "success": false, "error": "Failed to create support ticket" }
error:
{
"type": "error",
"payload": {
"message": "Invalid message format"
}
}