Error Handling - GoSentrix

{
  "error": {
    "code": "invalid_request",
    "message": "The request is invalid",
    "details": {
      "field": "email",
      "reason": "Invalid email format"
    }
  }
}

The GoSentrix API uses standard HTTP status codes and returns detailed error information.

HTTP Status Codes

Code	Meaning
`200`	Success
`201`	Created
`204`	No Content
`400`	Bad Request
`401`	Unauthorized
`403`	Forbidden
`404`	Not Found
`409`	Conflict
`422`	Unprocessable Entity
`429`	Too Many Requests
`500`	Internal Server Error

Error Response Format

All errors follow this format:

{
  "error": {
    "code": "invalid_request",
    "message": "The request is invalid",
    "details": {
      "field": "email",
      "reason": "Invalid email format"
    }
  }
}

Common Error Codes

See Error Codes Reference for a complete list.

Rate Limiting Errors

When rate limited, the response includes retry information:

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Too many requests",
    "retry_after": 60
  }
}

Best Practices

Always check HTTP status codes
Parse error responses for user-friendly messages
Implement exponential backoff for retries
Log errors for debugging
Handle rate limits gracefully