Error Handling

The Mando API uses standard HTTP status codes and returns detailed error information in JSON format.

HTTP Status Codes

Code	Description
200	Success
201	Created
400	Bad Request - Invalid parameters
401	Unauthorized - Invalid or missing API key
403	Forbidden - Insufficient permissions
404	Not Found - Resource doesn’t exist
409	Conflict - Resource already exists
422	Unprocessable Entity - Validation failed
429	Too Many Requests - Rate limited
500	Internal Server Error

Resource Errors

Code	Description
NOT_FOUND	Resource doesn’t exist
ALREADY_EXISTS	Duplicate resource
CONFLICT	Resource state conflict

Best Practices

1. Always catch errors - Never let API errors crash your application
2. Log error details - Include code, message, and request context
3. Use retry logic - Implement backoff for transient failures
4. Handle rate limits - Respect Retry-After headers
5. Validate inputs - Check data before sending to reduce errors