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](/guides/data-models/banking/overview). <Tip> **This is the read we recommend, and the one to build on.** Every family below also has its own endpoint — [Accounts](api:GET/executions/results/{execution_id}/financial/v1/accounts), [Cards](api:GET/executions/results/{execution_id}/financial/v1/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. </Tip> <Note> **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. </Note> | Status | Meaning | | :--- | :--- | | `200` | The position. | | `202` | `execution_still_processing` — this endpoint waits for the **whole** execution, unlike the per-family ones: a partial picture is a misleading one. | | `404` | No execution with that id for your application, or it has been deleted. | <Note> **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. </Note>