Error Handling
This guide explains how to handle errors when using WhatsAble APIs.HTTP Status Codes
All WhatsAble APIs use standard HTTP status codes:200 OK: Request successful400 Bad Request: Invalid request parameters401 Unauthorized: Invalid or missing API key403 Forbidden: Insufficient permissions404 Not Found: Resource not found429 Too Many Requests: Rate limit exceeded500 Internal Server Error: Server-side error
Error Response Format
All error responses follow this format:Common Error Codes
Authentication Errors
invalid_api_key: API key is invalid or expiredmissing_api_key: API key is missing from request
Request Errors
invalid_phone_number: Phone number format is incorrectinvalid_template: Template ID is invalid or not foundmissing_required_field: Required field is missinginvalid_variables: Template variables are invalid
Rate Limit Errors
rate_limit_exceeded: Too many requests in a time periodquota_exceeded: Monthly quota exceeded
Best Practices
- Always Check Status Codes: Don’t assume success
- Implement Retry Logic: For 429 and 500 errors
- Log Errors: For debugging and monitoring
- Handle Timeouts: Set appropriate timeout values
- Validate Input: Before making API calls