API Docs
/
No Results Found
Error Codes

Error Codes AI Tools

Open in ChatGPT

Open in ChatGPT to ask questions about this page

Open in Claude

Open in Claude to ask questions about this page

Copy as Markdown

Copy this page as markdown to use with AI assistants

View as Markdown

Open this page as markdown in a new tab

Arattai uses HTTP status codes to convey the success or failure of an API call. Status codes in the 2xx range signify success, 4xx codes indicate client-side errors caused by invalid or missing request information, and 5xx codes point to server-side errors.

HTTP Status Codes

Status Code Description
200 SuccessThe request was completed successfully.
204 No ContentThe request was completed successfully and there is no response body (used by cancel meeting, add/remove invitees, and send-message endpoints).
400 Bad RequestThe request could not be processed, usually due to a malformed, missing, or invalid parameter.
401 UnauthorizedThe request was rejected because the access token is missing, invalid, or expired.
403 ForbiddenThe authenticated user does not have permission to access the requested resource, or the granted OAuth scope does not cover this operation.
404 Not FoundThe requested resource (e.g., channel, meeting, or story ID) does not exist or is not accessible to the authenticated user.
429 Too Many RequestsThe request exceeded the endpoint's threshold limit. See the "Threshold limit" and "Lock period" notes on each endpoint.
500 Server ErrorArattai encountered an unexpected error while processing the request.

Known Error Codes

The following code values have been confirmed against real API responses. This list is not exhaustive — only codes with verified evidence are listed here.

Endpoint Status Code Cause
POST /restapi/v4/channels/{CHANNEL_ID}/messages 400 input_pattern_mismatch The contact.photo field was sent with an incomplete/truncated base64 string (e.g., copying the example value's trailing ... verbatim instead of a full base64 image).
POST /restapi/v4/meetings 400 extra_key_found A key not recognized by the request schema was included in the request body.