Error Handling

Understanding error responses and codes for proper error handling in your integration.

Error Response Structure

{
  "id": "E001",
  "code": "RESOURCE_NOT_FOUND",
  "message": "Requested resource is not found",
  "requestId": "req_12345",
  "debugMessage": "No resource found with the given ID",
  "subErrors": [
    {
      "fieldName": "resourceId",
      "message": "Resource ID is invalid",
      "debugMessage": "Resource ID 404 not found in the database"
    }
  ]
}

Field	Description
`id`	Error identifier (e.g. E100, E200)
`code`	Machine-readable code
`message`	Human-readable message
`requestId`	Correlation id for support
`debugMessage`	Extra debug detail
`subErrors`	Field-level validation errors

Brand Errors

Code	Description	Resolution
`E100`	Brand temporarily disabled	Wait and retry
`E101`	Brand not enabled for you	Contact support
`E102`	Brand not active	Do not display; refresh catalog

Order / Validation Errors

Code	Description	Resolution
`E150`	Denomination not available	Refresh catalog denominations
`E200`	Voucher generation failed	Retry after 1–2 minutes
`E201`	Provider polling failed	Same as E200
`E300`	Insufficient wallet balance	Top up wallet

Auth / Access Errors

HTTP	Typical Cause
`401`	Invalid/expired token or wrong credentials
`403`	IP not whitelisted
`400`	Malformed request body
`404`	Resource not found (or wrong environment)
`429`	Rate limit exceeded

Always include X-REQUEST-ID when contacting contact@rewardos.in.