Skip to main content

Reading Balances, Transactions, and Statements

Retrieve account balances, filtered transaction history, and statements through the Kuda Business API.

Written by Nosa O

Use account information endpoints to show balances, reconcile activity, export statements, and support finance operations.

These operations are read-only, but they still require secure server-side authentication.

Check account balance

Use ADMIN_RETRIEVE_MAIN_ACCOUNT_BALANCE to retrieve the main account balance.

{
  "serviceType": "ADMIN_RETRIEVE_MAIN_ACCOUNT_BALANCE",
  "requestRef": "BAL20260603001",
  "data": {}
}

Example response:

{
  "status": true,
  "message": "Operation successful",
  "data": {
    "ledgerBalance": 800000,
    "availableBalance": 800000,
    "withdrawableBalance": 800000
  }
}

Amounts are in kobo.

Retrieve filtered transactions

Use ADMIN_MAIN_ACCOUNT_FILTERED_TRANSACTIONS for paginated account history.

{
  "serviceType": "ADMIN_MAIN_ACCOUNT_FILTERED_TRANSACTIONS",
  "requestRef": "TXN20260603001",
  "data": {
    "pageNumber": "1",
    "pageSize": "25",
    "startDate": "2026-06-01",
    "endDate": "2026-06-03"
  }
}

Optional filters include:

  • startDate

  • endDate

  • transactionDate

  • referenceNumber

  • instrumentNumber

Use pagination for large date ranges.

Retrieve a statement

Use RETRIEVE_STATEMENT to request a statement for a date range.

{
  "serviceType": "RETRIEVE_STATEMENT",
  "requestRef": "STM20260603001",
  "data": {
    "fromDate": "2026-06-01",
    "toDate": "2026-06-30",
    "format": "Pdf"
  }
}

The API may respond that the statement is being sent to the registered inbox.

Use Pdf casing for PDF statements unless Kuda confirms another format for your account.

Fetch inflows and outflows

Some integrations may use dedicated inflow and outflow operations:

Operation

serviceType

Incoming transactions

ADMIN_ACCOUNT_INFLOW

Outgoing transactions

ADMIN_ACCOUNT_OUTFLOW

Use filtered transaction history when you need one unified ledger-style view.

Reconciliation tips

For finance and operations workflows, store:

  • referenceNumber

  • instrumentNumber

  • sessionId

  • transactionType

  • postingType

  • amount

  • narration

  • sender and beneficiary fields when available

  • opening and closing balances when returned

Use both referenceNumber and instrumentNumber during support investigations. They are not the same field.

Displaying balances

When showing balances to users:

  • label balances clearly

  • convert kobo to naira carefully

  • show the environment if users can access UAT and production

  • avoid showing stale cached balances as live balances

Common mistakes

  • Treating page totals as full-range totals when only one page was fetched.

  • Forgetting to paginate.

  • Mixing UAT and production transaction records.

  • Logging sensitive account data without access controls.

  • Assuming statement generation means immediate file download.

  • Treating instrumentNumber as a bank account number.

Did this answer your question?