⚠️ Important: This page lists common error codes for API development. For detailed guidance on handling errors, refer to our official documentation.
Common Error Codes
| Code | Description | Solution |
|---|---|---|
| 400 | Bad Request | Validate input parameters. Check input validation guide |
| 401 | Unauthorized | Ensure API keys or tokens are correctly configured. |
| 404 | Not Found | Confirm the requested resource exists. |
| 500 | Internal Server Error | Check server logs for detailed issues. |
HTTP Status Codes
HTTP status codes are standardized responses from servers. Here are key ones:
- 200 OK: Request succeeded. 🎉
- 400 Bad Request: Client error - invalid request. ⚠️
- 403 Forbidden: Access denied. 🔒
- 405 Method Not Allowed: Invalid HTTP method used. 🚫
- 502 Bad Gateway: Downstream service is unavailable. ⚠️
Custom Error Codes
Some APIs define unique error codes. For example:
- ERR_404_NOT_FOUND: Resource does not exist. Learn more
- ERR_500_INTERNAL: Server-side exception occurred. ⚠️
- ERR_429_TOO_MANY_REQUESTS: Rate limiting exceeded. ⚠️
Best Practices
✅ Always include detailed error messages in responses.
✅ Use consistent formatting for error codes.
✅ Link to relevant documentation for clarity.
✅ Monitor logs to identify recurring issues.
For advanced error handling techniques, visit our developer portal guide.