12345{ "status": "success", "message": "Your Airtime Purchase To 08031234567 Was Successful... Thank You", "data": { } }
| Field | Type | Meaning |
status | "success" or "failed" | Whether the request did what you asked |
message | string | Human-readable result. Safe to log, not to parse for logic |
data | object, array or null | The result. Shape depends on the endpoint; usually null on errors |
Content-Type: application/json. Form-encoded bodies fail with HTTP 500.message. Messages are written for people and may be reworded.| HTTP | Meaning | Typical action |
200 | Success, or accepted and queued | Read message; verify queued transactions |
201 | Invoice already paid (collections) | Treat as paid |
206 | Transfer queued, not yet confirmed | Poll Verify transfer |
400 | Missing or invalid field, not enabled, not found, or still pending | Fix the request, or check again later |
401 | Provider gave no final answer | Do not retry; verify the same tranx_id |
404 | Record not found | Check the reference you sent |
406 | Unauthorized token | Fix or rotate your token |
417 | Rejected or failed (and refunded when money moved) | Show the reason; a new attempt needs a new tranx_id |
500 | Unexpected server error | Retry later with the same tranx_id, then verify |
503 | Product temporarily unavailable or under maintenance | Retry later |
400 naming the field:1{ "status": "failed", "message": "bad request (tranx_id) not found in request param", "data": null }
1{ "status": "failed", "message": "(tranx_id) too short... please try again", "data": null }
503 (some bill endpoints use 417) and nothing is charged:1{ "status": "failed", "message": "Service Unavailable... Please Try Again Shortly", "data": null }
System Under Maintainance... Please Try Again Shortly. Retry later with the same tranx_id.