Banking apps and their data APIs

Mobile banking and neobank apps — the private APIs behind account balances, statements, cards, and transfers.

Banking apps turn a phone into a branch: balances, holdings and transfers rendered from private endpoints behind the home dashboard. Wise prices an international corridor before you send — POST /v2/pricing/estimates returns the mid-market rate, fee and guaranteedTargetAmount — and GET /v2/wallets/{walletRef}/jars splits a multi-currency balance into jars with availableAmount, reservedAmount and cashAmount per currencyCode. Angel One covers the broker side: POST /v2/portfolio/holdings lists demat holdings with qty, avgPrice, ltp and invested versus current market value, while GET /v1/wallet/summary separates cashBalance from collateral. Jar runs a gold locker instead of an account: GET /v1/holdings/snapshot marks grams held to market with volumeInMg, currentValue and changeInCurrentValue.

Frequently asked questions

Which banking apps here expose a balance API?

Wise does at GET /v2/wallets/{walletRef}/jars — per-currency jars with availableAmount, reservedAmount, cashAmount and totalWorth. Angel One's GET /v1/wallet/summary splits cashBalance, collateral and tradingBalance with the withdrawable rupee amount, and Jar's GET /v1/holdings/snapshot marks gold grams to market (volumeInMg, currentValue, investedValue).

Can I price a transfer before booking it?

Yes — Wise POST /v2/pricing/estimates prices the corridor at the mid-market rate plus fee, returning sourceCurrency, targetCurrency, rate, fee and guaranteedTargetAmount so the send calculator can lock targetAmount before booking.

Do these apps share a common auth pattern?

All are token-based but shaped to their flow. Wise attaches a Bearer access token rotated by a refresh token; Angel One gates the session with a PIN (POST /v1/session/verify-pin) and layers risk limits (POST /v2/risk/limits); Jar signs in over OTP and attaches the issued Bearer token thereafter.