Documentation
Moolre lets you move money, collect payments, sell airtime and data, send messages, and build USSD experiences from one API surface. Use the guides when you need context, then switch to API Reference when you need exact request and response details.
Live APIs are available at https://api.moolre.com, and sandbox APIs are available at https://sandbox.moolre.com.
Jump right in

Quickstart
Make your first authenticated request and understand environments.

Send money
Validate names, initiate transfers, and check transfer status.

Collect payments
Create payment IDs, bank numbers, links, and payment checks.

Sales
Set up your service, sell airtime and data, and look up bundles.

Account wallets
Manage wallets, inspect wallet status, and list transactions.

Messaging
Send SMS, manage sender IDs, and automate WhatsApp messages.

USSD
Build offline menus and simulate customer journeys.
Postman collection
Download the generated collection, then import the live or sandbox environment for the workspace you want to test.
Moolre API Postman Collection
Includes documented endpoints, headers, sample bodies, and response examples generated from the docs.
Production base URL and credential variables.
Sandbox base URL for simulated requests.
Support
Send questions, integration issues, and feedback to the Moolre support channels.
Requests and responses
Request bodies and responses use JSON. Most Moolre responses follow this envelope:
{
"status": 1,
"code": "SMS01",
"message": "Success",
"data": { ... },
"go": null,
"meta": { "requestid": "req_c68f4c66115c26725c796242", "notices": [] }
}| Field | Description |
|---|---|
| status | Integer that indicates success or failure. 1 means success, 0 means failure. |
| code | Unique response identifier for the result returned by the endpoint. |
| message | Human-readable description of the response. |
| data | Payload returned by the request. This can be a string, array, or object. |
| go | Optional navigation hint or next action value. |
Authentication
Moolre authenticates requests with API keys passed in headers. Depending on the endpoint, you may useX-API-USER,X-API-KEY,X-API-PUBKEY, orX-API-VASKEY.
