Overview
The Cuey API uses standard HTTP status codes and returns error responses in a consistent format.Error Response Format
All error responses follow this structure:HTTP Status Codes
| Code | Description |
|---|---|
200 | OK - Request succeeded |
201 | Created - Resource created successfully |
400 | Bad Request - Invalid request data |
401 | Unauthorized - Invalid or missing API key |
404 | Not Found - Resource not found |
500 | Internal Server Error - Server error |
Error Codes
UNAUTHORIZED
Returned when the API key is invalid or missing. Status Code:401
Example Response:
- Missing
Authorizationheader - Invalid API key
- Expired or revoked API key
NOT_FOUND
Returned when a requested resource doesn’t exist. Status Code:404
Example Response:
- Invalid resource ID
- Resource belongs to another team
- Resource was deleted
VALIDATION_ERROR
Returned when request validation fails. Status Code:400
Example Response:
- Invalid field values
- Missing required fields
- Invalid data types
- Validation rule violations
BAD_REQUEST
Returned when the request is invalid (e.g., business logic violations). Status Code:400
Example Response:
- Trying to update a non-pending event
- Trying to delete an event created by a cron
- Requesting an out-of-range page number
INTERNAL_SERVER_ERROR
Returned when a server error occurs. Status Code:500
Example Response:
- Database errors
- Requesting an out-of-range page number
- Unexpected server failures