Skip to content

Changelog / Releases

App features, API updates, SDK releases, and documentation improvements.

View as Markdown

13 updates

  1. API UpdateBreaking Change
    API

    Response envelope change: request ID and notices move into meta

    Every JSON response now ends with a meta object that holds meta.requestid and meta.notices. The top-level request_id and notices fields and the outcome field are gone. Webhook payloads are unchanged.

    Permalink

    What changed

    • meta is always present on every JSON response, as the last field. It holds meta.requestid (the same value as the X-Request-Id response header; your own X-Request-Id if you sent a valid one) and meta.notices (always an array, [] when there is nothing to report; each notice is `{ code, message, docs? }`).
    • The top-level request_id and notices fields are removed from API responses. They were added earlier on 15 November 2026 and now live inside meta.
    • The outcome field is removed everywhere.
    • error (failures) stays at the top level, before meta, unchanged. The X-Request-Id response header is still sent.
    • Idempotent replays (same Idempotency-Key and same body) carry meta.replayed: true. It replaces the top-level `replayed` field, which is removed. It is present only on replays. `data.replayed` on bulk payouts (BLK02) and invoice create (INV02) is resource data and stays where it is.
    • Webhook payloads: the top-level `notices` moved into `meta.notices` (`"meta": {"notices": []}`). event_id, event, created and all other fields stay at the top level. The X-Moolre-Signature header, an HMAC over the raw body, is unchanged. Webhooks have no requestid.

    SDK releases

    • The official SDKs read `meta.requestid`, `meta.notices` and `meta.replayed`, and webhook `meta.notices` (falling back to the old top-level fields and the X-Request-Id header). Their `requestId` / `request_id` and `notices` properties are unchanged.
    • Published: Node.js `@moolre/sdk` 0.1.3 on npm (`npm install @moolre/sdk`; 0.1.3 only corrects the repository link to github.com/moolrehq/sdk), PHP `moolre/moolre-php` 1.1.2 on Packagist (`composer require moolre/moolre-php`) and the browser checkout `@moolre/moolrejs` 1.1.1 on npm (`npm install @moolre/moolrejs`).
    • Python `moolre` 0.1.2 is on PyPI since 17 November 2026 (`pip install moolre`). The files on PyPI are the same as the downloads on the SDKs page, which lists the SHA-256 checksum of every file.

    Migration

    • Read the request id from `meta.requestid` instead of `request_id`, and the notices from `meta.notices` instead of `notices`. The X-Request-Id header carries the same value if you prefer it.
    • Stop reading `outcome`. Decide the result from `status`, `code` and `data.txstatus` (0 pending, 1 succeeded, 2 failed).
    • Treat these codes as pending, never as failed, because the result is unknown and the transaction may still succeed: PY01, PY02, TR01, TR02, TP11, TP18, APY10, APY16, ASL06 and SYS500. Check the status by externalref and never resend blindly.
    • Status 1 with TR08, OBGH01, OTGH01, OBNG01, GHQ03 or OM03 is final success. Any other status 1 is an accepted, unfinished request: treat it as pending.
    • The official SDKs keep their property names (requestId, request_id, notices) and read meta first, then the old top-level fields, then the X-Request-Id header, so SDK users need no code change.
    • If you read a top-level `replayed`, read `meta.replayed` instead (true only on idempotent replays). If you read a webhook payload top-level `notices`, read `meta.notices`.

    Related documentation

  2. API UpdateNew FeaturePlugin/SDK Release
    API

    Bulk payouts, invoices, signed webhooks and request IDs

    Pay up to 500 recipients in one request, create invoices, verify webhooks with a signature, and trace every call with a request ID. Everything is additive and backwards compatible: existing requests and responses are unchanged.

    Permalink
  3. API Update
    API

    Payer details in payment webhooks

    Payment callbacks now include the payer’s name, network, and institution, so you can see who paid and how without an extra lookup.

    Permalink
  4. New FeatureAPI Update
    API

    Airtime and Data Sales APIs

    Sell airtime and mobile data bundles on MTN, Telecel, and AT from your Moolre wallet, look up available bundles, and check the outcome of every sale.

    Permalink
  5. Improvement
    Documentation

    New use cases: airtime and data top-ups, rewards and incentives

    Two new end-to-end use cases show how to build with the Sales APIs, and the existing use case pages have a refreshed, more consistent layout.

    Permalink
  6. Improvement
    Documentation

    Create wallets in the Moolre portal

    For compliance reasons, Create Account has been removed from the public API reference. Create your wallets in the Moolre portal instead.

    Permalink
  7. Improvement
    Documentation

    IP Whitelisting for Disbursements guide

    A new step-by-step guide explains how to authorize your servers to initiate disbursements through a specific API Service.

    Permalink
  8. API UpdateImprovement
    Documentation

    Payment webhook failure guidance and callback source IPs

    The Payment Webhook reference now documents failed payment callbacks alongside successful payments, with callback source IPs and section navigation in one place.

    Permalink
  9. New FeatureAPI Update
    Documentation

    Bank account and Payment ID transaction documentation

    New reference pages explain how to list bank accounts and retrieve transactions for bank accounts and Payment IDs.

    Permalink
  10. API Update
    Documentation

    SMS delivery network guidance

    The SMS reference now explains the optional delivery network, the TELECEL default, and the fallback for unapproved MTN requests.

    Permalink
  11. New FeatureImprovement
    App

    Wallet-Specific ID Verification

    Verify each wallet individually, reuse verified documents for wallets belonging to the same business, and share verification links with wallet owners.

    Permalink
  12. New FeatureAPI Update
    App

    Wallet-Specific API Key Generation

    Connect each wallet to its own API Service and generate wallet-specific credentials so integrations operate on the intended wallet.

    Permalink
  13. Improvement
    Documentation

    SDK documentation refinements

    SDK pages have clearer integration guidance, consistent headers, and links to the relevant packages and repositories.

    Permalink