API Reference
Errors
Error codes and troubleshooting.
Errors
QANATIX returns standard HTTP status codes with a detail field.
Error response format
{
"detail": "Entity not found"
}Validation errors include field-level details:
{
"detail": [
{
"loc": ["body", "records", 0, "name"],
"msg": "field required",
"type": "value_error.missing"
}
]
}Status codes
| Code | Meaning | Common causes |
|---|---|---|
| 200 | Success | — |
| 201 | Created | Entity or key created |
| 400 | Bad Request | Invalid JSON, missing required fields, malformed query |
| 401 | Unauthorized | Missing or invalid API key |
| 403 | Forbidden | API key lacks required scope |
| 404 | Not Found | Entity, vertical, or connector not found |
| 409 | Conflict | Duplicate entity (content hash collision) |
| 413 | Payload Too Large | Batch exceeds 5,000 records or file > 50 MB |
| 422 | Validation Error | Request body fails Pydantic validation |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Error | Server error — contact support |
Request ID
Every response includes an X-Request-Id header. Include this when reporting issues.
X-Request-Id: req_abc123def456