Errors & codes

Response shapes

Operation	JSON shape
Create (sync or async)	`status`, `response_code`, `response_message`, `data`
Status	`status`, `response_code`, `response_message`, `data`
List	`status`, `data`, `pagination`
Wallet balance	`status`, `data`, `total`
Bill validate / packages	`status`, `data`
Bill status	`status`, `response_code`, `response_message`, `data`

Transaction codes

Inside create and status responses, response_code maps to status:

`response_code`	`status`	Meaning
`00`	`success`	Successful
`01`	`failed`	Failed
`02`	`pending`	Still processing

Failed example (status):


{
  "status": "failed",
  "response_code": "01",
  "response_message": "Failed",
  "data": {
    "request_id": "req-20260517-003",
    "internal_reference": "019262ab-7c4d-7000-8000-000000000001"
  }
}

HTTP status codes

Status	When
`200`	Success (sync or async create, status, list, balance)
`400`	Invalid JSON or validation error
`401`	Missing or invalid API key / secret
`403`	Credential cannot access this merchant or transaction
`404`	Merchant or transaction not found
`422`	Duplicate `client_request_id` or validation error
`500`	Server error — retry with backoff
`503`	Temporary overload — retry with backoff

Health check


GET /ext/breeze/v1/healthz

No authentication required. Use for uptime monitoring only.