Skip to main content
Every error response follows the same envelope: 
{
  "success": false,
  "statusCode": 401,
  "message": "Request is missing api key",
  "timestamp": "2026-07-09T00:00:00.000Z",
  "path": ""
}

​
Common errors

{
  "success": false,
  "statusCode": 401,
  "message": "Request is missing api key",
  "timestamp": "2026-07-09T00:00:00.000Z",
  "path": ""
}
Check that the api-key header is present and holds a valid secret key for the environment (test vs. live) you’re calling.
Returned when a required field is missing or malformed, or when an operation conflicts with existing state — e.g. requesting a second active bank account for a customer/currency pair that already has one.
Returned when a referenced resource — a customer, account, or transaction reference — doesn’t exist.
{
  "success": false,
  "statusCode": 422,
  "message": "Insufficient Balance"
}
Returned when your wallet balance can’t cover the requested amount and fees.
{
  "success": false,
  "statusCode": 500,
  "message": "Internal server error",
  "timestamp": "2026-07-09T00:00:00.000Z",
  "path": ""
}
An unexpected error occurred on Reeple’s end.
A 500 or gateway error (e.g. 502) on a payout or bill payment request does not necessarily mean it failed — it can also mean the response was lost after Reeple already processed it. Verify the transaction (e.g. via Get transaction by reference) before retrying, to avoid double-processing.