Mono · Flutterwave
Keep Mono · Flutterwave in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
19 ways to read, 5 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Mono · Flutterwave, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Request income analysisApproval by rule
- Request statement insightsApproval by rule
- Get account balanceRead
Example flow
- Mono · Flutterwave · Get account balanceDone
- Mono · Flutterwave · Request income analysisNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Mono · Flutterwave.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Mono · Flutterwave
- Mono · Flutterwave's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Mono test account before you go live.
For developers
Technical detail
Mono open-banking data for linked Nigerian (and Ghanaian, Kenyan, South African) bank accounts: accounts, identity, balances, transactions, statements, income and enrichment.
Mono API docs- Source actions
- 19
- Destination actions
- 5
- Data types
- 22
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Accounts2
- Get account detailsSource
Account, institution, customer and data status for one linked account.
- List linked accountsSource
All bank accounts linked to the Mono app, newest first.
Assets1
- Get investment assetsSource
Holdings and balances of a linked investment account.
Balances1
- Get account balanceSource
Current balance of a linked account; real-time refresh is optional.
Banks1
- List NIP banksSource
Banks on the NIBSS Instant Payment (NIP) network with their NIP codes.
Credits1
- Get monthly inflowsSource
Total inflow into the account grouped by month.
Customer transactions1
- List customer transactionsSource
Transactions across a customer's linked accounts for the last 1-12 months, optionally for one account; each record carries the account it came from.
Customers2
- Get customerSource
One Mono customer by ID.
- List customersSource
Customers created in the Mono app.
Debits1
- Get monthly outflowsSource
Total outflow from the account grouped by month.
Earnings1
- List investment earningsSource
Earnings (sales and payouts) on a linked investment account.
Enrichment jobs1
- Get enrichment jobSource
Status of a categorisation, metadata or statement insight job.
Enrichment records1
- List enrichment recordsSource
Results of a completed enrichment job (for example statement insights), available for 60 minutes.
Identities1
- Get account identitySource
Identity of the account holder as held by the bank (name, BVN, phone, address, date of birth).
Income records1
- List income recordsSource
Completed income analyses for the account.
Income1
- Request income analysisDestinationNot retried automaticallyApproval before production
Starts Mono's income analysis for the account; results arrive by webhook and in income records.
Institutions1
- List supported institutionsSource
Banks Mono supports, with country, NIP and bank codes, login methods and product scopes (financial data, direct debit).
Statement insights1
- Request statement insightsDestinationNot retried automaticallyApproval before production
Starts statement insight analysis; read the result with List enrichment records.
Statement jobs1
- Get statement PDF jobSource
Status and location of a statement PDF job.
Statement pdfs1
- Request statement PDFDestinationProvider duplicate protectionApproval before production
Starts building a 1-12 month PDF bank statement and returns the job to poll.
Statements1
- List statement transactionsSource
Bank statement for the last 1-12 months as JSON transactions.
Transaction categorisation1
- Categorise transactionsDestinationNot retried automaticallyApproval before production
Asks Mono to categorise the account's transactions; re-read transactions after the webhook.
Transaction metadata1
- Enrich transaction metadataDestinationNot retried automaticallyApproval before production
Asks Mono to add metadata to the account's transactions.
Transactions1
- List transactionsSourceIncremental
Account transactions, optionally between dates, by type or narration; most recent first.
Access and limits
- Authentication
- Mono secret key (mono-sec-key header)
- Plans and access
- Mono business account with Connect enabled; income, enrichment, investment and real-time data depend on the subscription plan. The secret key reads every account linked to the app. Accounts must first be linked by the end customer through Mono Connect.
- Test environment
- Sandbox and production share api.withmono.com; a test secret key reads sandbox accounts linked with Mono's sandbox credentials.
- Rate limits
- Mono does not publish fixed rate limits; Nexra backs off on HTTP 429 and retries reads with Retry-After.
- Pagination
- Accounts, customers, income records and transactions use page numbers until meta.next is null; transactions also accept limit.
- Provider events
- Mono webhooks for account connection, data sync, income, statement insights and enrichment events, verified with mono-webhook-secret. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Account linking, re-authorisation, partner session APIs, unlinking and creditworthiness checks are intentionally not automated.
- Income, statement PDF, categorisation, metadata and statement insights are asynchronous: Nexra starts the job and returns its status; results arrive by webhook or later reads.
- Mono has no documented data-sync endpoint in v2; the realtime input sends the documented x-realtime header to refresh data from the bank.
- Mono does not document the account list item, income record or enrichment record schemas; those fields are read defensively.
- Account-number, name, email and phone list filters are not exposed so personal data stays out of URLs.
- Mono's bank-data API is read-mostly and small; Nexra covers every documented read. Customer create, update and delete, KYC lookups (BVN, NIN, TIN, CAC, passport, driver's licence, account number, credit history, address), telco data, Prove and watchlist screening are not implemented.
- Not implemented by design: DirectPay one-time payments, direct debit mandates and debits, payouts, disbursements, WhatsApp payments and account unlinking. Payment-product transactions are read-only (customer_transactions.list).
- Mono documents example responses but not full schemas for customer transactions, institutions and NIP banks; those fields follow the published examples.
- Amounts are in minor units (kobo, pesewa, cents).
Developer reference
- Create the Mono credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Mono · Flutterwave, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/mono and the Connections API.