HTTP Status Codes
The API uses standard HTTP status codes. Because the AI Helpdesk API is read-only, only 200 is used in the 2xx range.
Error Response Body
When an error occurs, the API returns the following JSON body:
Response Fields
Common Errors
Authentication Error (401)
Cause: The X-API-Key header is missing or contains an invalid value.
Resource Not Found (404)
Cause: The path parameter does not exist or belongs to a different tenant. This applies to sessionKey, docId, typePath, integrationId, and other path parameters.
Invalid Parameters (400)
Cause: An enum query parameter such as status or assigneeType is out of range. It also occurs when limit is outside the allowed range (1..100, or 1..500 for procedures).
Best Practices
- Always branch on the
ok field — do not infer success purely from HTTP code.
- Log the
error message and translate it into a user-facing message as appropriate.
- Do not auto-retry 401 — it requires a key rotation. Surface it to operators.
- Do not auto-retry 404 — the caller logic is at fault.
- Avoid logging sensitive information such as full API keys.
Last modified on October 9, 2026