Guides
Errors
How the API reports errors, and the codes you can branch on.
Successful responses have "status": true and a data object. Errors use standard HTTP codes with "status": false, a readable message and a stable code you can branch on.
422 Unprocessable Entity
{
"status": false,
"message": "amount must be a whole number of kobo, at least 100",
"code": "invalid_amount"
}HTTP status codes
| Code | Meaning |
|---|---|
| 200, 201 | It worked. |
| 400 | The request body isn't valid JSON. |
| 401 | The key is missing, wrong or for the wrong mode. |
| 404 | The thing you asked for doesn't exist. |
| 422 | A field is missing or invalid. Read code and message. |
| 429 | Too many requests. Slow down and retry. |
| 5xx | Something went wrong on our side. Retry with the same idempotency key. |
Error codes
| code | What to do |
|---|---|
unauthorized | Check your key and that it matches the base URL. |
invalid_amount | Send a whole number of kobo, at least 100. |
invalid_email | Send a valid customer email. |
invalid_account | Send a 10-digit account number and a bank code. |
account_not_found | The account doesn't exist at that bank. |
invalid_recipient | Check the recipient's details before sending. |
not_found | Check the reference or path. |