Appearance
Error Codes Reference
FreshHTTP Status Codes
Client Errors (4xx)
| Code | Name | Description | Common Fix |
|---|---|---|---|
| 400 | Bad Request | Invalid or malformed request | Check request parameters and payload format |
| 401 | Unauthorized | Missing or invalid credentials/token | Refresh token or re-authenticate |
| 403 | Forbidden | Insufficient permissions | Verify user role and workspace access |
| 429 | Too Many Requests | Rate limit exceeded | Implement exponential backoff; use automation token |
Server Errors (5xx)
| Code | Name | Description | Common Fix |
|---|---|---|---|
| 500 | Internal Server Error | Unexpected server-side error | Check payload validity; contact support if persistent |
Error Response Decision Tree
Error Response Format
All errors follow this structure:
json
{
"status": {
"error_code": "invalid_request",
"http_code": 400,
"message": "The request was invalid or malformed"
},
"data": null
}Rate Limiting
Rate Limits
The API enforces rate limits. When you receive a 429 response:
- Stop sending requests immediately
- Wait with exponential backoff (1s, 2s, 4s, 8s...)
- Consider upgrading to an automation token for higher limits