Error Handling
Error codes, responses, and troubleshooting
Error Handling
Understanding API error responses and how to troubleshoot issues.
HTTP Status Codes
200 OK
Request succeeded
201 Created
Resource created successfully
400 Bad Request
Invalid request parameters or body
401 Unauthorized
Missing or invalid authentication
403 Forbidden
Authenticated but not authorized (e.g., domain not in your account)
404 Not Found
Resource doesn't exist
429 Too Many Requests
Rate limit exceeded (see Retry-After header)
500 Server Error
Internal server error — retry with backoff
Error Response Format
{
"message": "Validation failed",
"errors": {
"domain_name": ["Domain name is required"],
"automation_level": ["Invalid automation level"]
}
}Common Error Scenarios
Invalid Token
Solution: Generate a new token in Settings → API Access. Expired tokens must be recreated.
Domain Not Found
Solution: Use the exact domain name. API only returns domains in your account (no enumeration).
SPF Lookup Limit Exceeded
Solution: Consolidate SPF sources. Use the SPF Flattener tool to reduce nested includes.
DNS Provider Authentication Failed
Solution: Re-authenticate in Settings. Verify API tokens are still valid on the DNS provider.