One recharge and its current status — see the example on the right.
200 OK · failed recharge
Alternate outcome for the same call — the second Response tab.
4xx / 5xx
{ "success": false, "error": { "code": "…", "message": "…" } } —
every code is listed under
Error Codes.
📘
Good to know
status is SUCCESS, PENDING or FAILED. This endpoint reads the stored state and never calls the operator. Operator callbacks update a recharge within seconds, and every PENDING recharge is re-checked every 2 minutes, so polling more often than every 30 seconds gains nothing. refunded: true on a FAILED recharge means the debit is back in your MAIN wallet, or was never taken.
failure_code (FAILED only) is stable and safe to branch on: INVALID_NUMBER (wrong number or operator), INVALID_AMOUNT (plan or denomination not accepted), DUPLICATE_RECHARGE (the same number and amount were recharged moments ago; wait before retrying), OPERATOR_UNAVAILABLE (the operator is down; retry later), INSUFFICIENT_BALANCE, NOT_SUBMITTED (never reached the operator) and OPERATOR_FAILED (any other operator decline). After a FAILED recharge a fresh attempt needs a newclient_reference.