Implemented

Accounting, billing & payments

Mono

Mono open-banking data for linked Nigerian (and Ghanaian, Kenyan, South African) bank accounts: accounts, identity, balances, transactions, statements, income and enrichment.

Feed verified bank data into underwriting, reconciliation and onboarding flows without manual statement uploads.

Build a flow with Mono Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

accounts

Get account details
Source
Account, institution, customer and data status for one linked account.
accounts.get
List linked accounts
Source
All bank accounts linked to the Mono app, newest first.
accounts.list

assets

Get investment assets
Source
Holdings and balances of a linked investment account.
assets.get

balances

Get account balance
Source
Current balance of a linked account; real-time refresh is optional.
balances.get

credits

Get monthly inflows
Source
Total inflow into the account grouped by month.
credits.get

customers

Get customer
Source
One Mono customer by ID.
customers.get
List customers
Source
Customers created in the Mono app.
customers.list

debits

Get monthly outflows
Source
Total outflow from the account grouped by month.
debits.get

earnings

List investment earnings
Source
Earnings (sales and payouts) on a linked investment account.
earnings.list

enrichment jobs

Get enrichment job
Source
Status of a categorisation, metadata or statement insight job.
enrichment_jobs.get

enrichment records

List enrichment records
Source
Results of a completed enrichment job (for example statement insights), available for 60 minutes.
enrichment_records.list

identities

Get account identity
Source
Identity of the account holder as held by the bank (name, BVN, phone, address, date of birth).
identities.get

income records

List income records
Source
Completed income analyses for the account.
income_records.list

income

Request income analysis
Destination
Not retried automatically
Approval before production
Starts Mono's income analysis for the account; results arrive by webhook and in income records.
income.generate

statement insights

Request statement insights
Destination
Not retried automatically
Approval before production
Starts statement insight analysis; read the result with List enrichment records.
statement_insights.generate

statement jobs

Get statement PDF job
Source
Status and location of a statement PDF job.
statement_jobs.get

statement pdfs

Request statement PDF
Destination
Provider duplicate protection
Approval before production
Starts building a 1-12 month PDF bank statement and returns the job to poll.
statement_pdfs.generate

statements

List statement transactions
Source
Bank statement for the last 1-12 months as JSON transactions.
statements.list

transaction categorisation

Categorise transactions
Destination
Not retried automatically
Approval before production
Asks Mono to categorise the account's transactions; re-read transactions after the webhook.
transaction_categorisation.generate

transaction metadata

Enrich transaction metadata
Destination
Not retried automatically
Approval before production
Asks Mono to add metadata to the account's transactions.
transaction_metadata.generate

transactions

List transactions
Source
Incremental
Account transactions, optionally between dates, by type or narration; most recent first.
transactions.list

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. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Account linking, re-authorisation, partner session APIs, unlinking, creditworthiness checks, customer create or update, direct debit and payment APIs 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.
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, 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

Mono docsAPI reference Mono docsAuthentication Mono docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/mono and the Connections API.