Skip to content
Mando API

Error Handling

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

HTTP Status Codes

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

Resource Errors

Section titled “Resource Errors”
CodeDescription
NOT_FOUNDResource doesn’t exist
ALREADY_EXISTSDuplicate resource
CONFLICTResource state conflict

Best Practices

Section titled “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