CashflowAnalytics
GET
https://test.api.neotek.sa/b2b-unified/v1/analytics/cashflowSandbox URL · in Production call https://api.neotek.sa
Daily credit and debit aggregates, pre-computed during the transaction sync. No pagination.
Query parameters:
| Parameter | Required | Description |
|---|---|---|
bankCode | Required | which bank holds the account: RJHISARI or ARNBSARI |
accountIban | Required | the account to read |
fromDate | Required | start of the range, as YYYY-MM-DD |
toDate | Optional | end of the range. Defaults to yesterday, and is capped at T-1 |
Headers:
| Parameter | Required | Description |
|---|---|---|
authorization | Required | Bearer <ACCESS_TOKEN> |
cURL
curl -G 'https://test.api.neotek.sa/b2b-unified/v1/analytics/cashflow' \ --header 'authorization: Bearer <ACCESS_TOKEN>' \ -d 'bankCode=ARNBSARI' \ -d 'accountIban=SA1030000012345678901004' \ -d 'fromDate=2026-02-01' \ -d 'toDate=2026-02-28'Each entry in dailyCashflows carries:
date– the day, asYYYY-MM-DDtotalCredit– sum of everything incoming that daytotalDebit– sum of everything outgoingcreditCount,debitCount– how many of eachnetFlow–totalCreditminustotalDebit; negative means a net outflowcurrency– the currency code
summary carries the same fields aggregated across the whole range.
Response (trimmed to one day)
JSON
{ "success": true, "code": "SUCCESS", "message": "Cashflow analytics retrieved successfully", "accountIban": "SA1030000012345678901004", "fromDate": "2026-02-01", "toDate": "2026-02-28", "dailyCashflows": [ { "date": "2026-02-01", "totalCredit": "125000.00", "totalDebit": "89500.50", "creditCount": 15, "debitCount": 42, "netFlow": "35499.50", "currency": "SAR" } ], "summary": { "totalCredit": "175000.00", "totalDebit": "161800.50", "creditCount": 23, "debitCount": 67, "netFlow": "13199.50", "currency": "SAR" }}Errors — both services share the same failure shape and codes; see Analytics → Errors.