Check which accounts the user can connect
Name the bank, country and account type your app needs. For a wallet, specify the network and asset. Ask which sources are available for your integration and how a user grants or withdraws access.
BLUWHALE FOR DEVELOPERS
Account Aggregation API for Bank Accounts and Crypto Wallets
Building an app that shows a bank balance alongside a crypto wallet? Start with the sources your customer can connect and the records each source can share. Bluwhale’s developer offering includes permissioned bank, wallet and exchange data, REST API access and prebuilt schemas. Confirm coverage for your first use case before you build.
BUILT WITH BLUWHALE
What can an account aggregation API tell your app?
A balance tells you how much a source reported at a particular time. A transaction history helps explain how it got there. If your feature needs both, ask for a sample of each from the institution or network you plan to support.
Ask for a dated sample record
Bluwhale describes REST API access and prebuilt schemas for developers. Ask for the applicable schema and a representative response. Verify how it identifies an account, distinguishes posted from available balances, records currency and reports when the value was observed.
Choose the question an agent should answer
For a balance summary, the agent needs to know which accounts the customer included and how current each balance is. To explain a change, it also needs the relevant transactions. Confirm the available history before promising that explanation in your app.
HOW IT WORKS
Bank and wallet data in one balance view
Suppose a bank reports a posted balance of $825 on Tuesday at 9 a.m. and a wallet last reported 120 USDC on Monday at 6 p.m., both in UTC. A useful first screen shows the two amounts, their units and their dates. This example describes what to ask a provider to demonstrate.
01
Identify each source
Request a bank account reference and the type of balance it reports. For the wallet, confirm the network, address, asset and token quantity. Ask Bluwhale which of those records it can supply for your intended sources.
02
Agree on read access
Show the customer which accounts and records the balance view will use. Define how the app will handle a disconnect, including how it labels the last balance it received.
03
Keep units and times visible
The bank reported USD and the wallet reported USDC at an earlier time. Before showing a combined USD value, obtain a dated conversion quote and explain how you handle the older observation.
04
Try a refresh failure
Pause the wallet update in your test case. The app should still show the bank’s $825 balance. If it displays the earlier 120 USDC, label it with Monday’s timestamp. A missing update is no evidence that the wallet is empty.
Account Aggregation API workflow
01Account scope
02User permission
03Structured records
04Product workflow
A conceptual workflow. Available capabilities depend on the selected integration.
PRACTICAL USE CASES
Where bank and wallet data can help
Bluwhale connects account context to a broader financial ecosystem. These are practical directions for an integration; the sources and actions needed for each should be scoped with the developer team.
Personal finance experiences
Bring the accounts a user authorizes into a clearer financial view. A useful first release can focus on explaining what is connected and which balances or records inform the experience.
Financial assistants
Ground an assistant in the account context the user has shared. Define the question, relevant records and reporting period so the answer relates to the user’s actual financial situation.
Agent-powered products
Use permissioned context as the input to a defined agent task. Keep data access and permission to execute an action distinct in the product journey.
YOUR QUESTIONS, ANSWERED
Account Aggregation API questions
Understand the workflow and choose your next step with Bluwhale.
What is an account aggregation API?
It gives an application a programmatic way to work with information from connected financial accounts. Bluwhale places user-permissioned account data within a developer ecosystem that also supports financial AI agents.
Which banks and wallet networks can my app use?
Bluwhale describes access to permissioned data from banks, wallets and exchanges. Bring the institution, country, network and account type you need. Confirm supported fields, refresh timing and available transaction history with the developer team for that combination.
Is account aggregation the same as moving money?
No. Reading financial records and executing a transaction are different capabilities. Scope the data your application needs separately from any agent tools or transaction permissions it may request.
What should I ask for in an account aggregation API demo?
Bring one user question and two representative sources. Ask for the records behind the answer, their timestamps and the result when one source disconnects. If your app also needs transaction history, specify the period and ask to see an example covering it.
EXPLORE BLUWHALE
Continue with the right financial experience
YOUR NEXT STEP
Check coverage for your first integration
Bring the bank account type, wallet network and user question your product needs to support. Ask the Bluwhale team for a representative response and the access requirements for that combination.