Transactions
Airtime and data purchases live under the /v1/transactions API. All routes share the same authentication headers and request body shape.
Sync vs async
Sync: the API runs vending before responding. You get the final outcome in the create response.
| Route | Notes |
|---|---|
POST /v1/transactions/airtime/sync | Airtime only |
POST /v1/transactions/data/sync | Data only (plan_code required) |
POST /v1/transactions | Bill products only: ELECTRICITY, CABLE, BETTING — see Bill payments overview |
POST /v1/transactions/verify | Optional bill customer check (no charge) — see Bill payments |
Async: the API stores the transaction, enqueues it, and returns immediately with HTTP 200 and response_code 02 (pending). Poll status until final. See Airtime Async.
| Route | Notes |
|---|---|
POST /v1/transactions | product: airtime or data |
POST /v1/transactions/airtime/async | Forces product: airtime |
POST /v1/transactions/data/async | Forces product: data |
Guides
| Topic | Page |
|---|---|
| Sync airtime & data | Airtime |
| Async create, status, list | Airtime Async |
| Full product catalog | Catalog |
| Data bundle catalog | Data plans |
Last updated on