Financial Position
One answer with everything financial the execution retrieved — the unified position of your customer at that institution: profile, accounts, cards, deposits, loans, investment accounts, stocks, funds, pension plans and direct debits, each family under its own key. The keys are described in Banking.
This is the read we recommend, and the one to build on. Every family below also has its own endpoint — Accounts, Cards, and the rest — and they answer the same records. The difference is the number of requests: one here, up to ten there, for the same execution and the same data.
Reach for a single family when you genuinely want one — a balance check, a card list — and for anything that reasons over the whole picture (scoring, underwriting, affordability) come here.
Only what was requested appears. The object is built from what this execution actually retrieved: a family that was not asked for, or that the source did not answer, is simply absent. Nothing here fails because a feature is missing — so read the keys rather than assuming them.
Server to server only. This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read.
Authentication
Path parameters
Response
200 OK
Everything the execution retrieved from the institution, assembled into one object: accounts, cards, deposits, loans, investments and direct debits, each under its own family. A family the execution did not ask for is simply absent.