> For the complete documentation index, see [llms.txt](https://doc.api.tieto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.api.tieto.com/api-references/openfinance/extended-account-information-service.md). # Extended Account Information Service The regulated account service is deliberately narrow: payment accounts, and only the data the directive obliges a bank to hand over. Extended account information is what you publish when that narrowness starts costing your tenant banks business — savings, lending and investment products, deeper transaction history, and richer detail on the accounts already in scope. Scope here is a commercial decision rather than a regulatory one: which products, which fields, how far back history reaches, and what each third party pays for it. It is sold, metered and rate-limited like any other premium product, and a product defined once can be offered by every tenant that wants it. Because extended access runs through the same consent model as the regulatory Account Information Service, the banks offering this service can keep delegating consent management to the platform exactly as they already do — no second mechanism to build and operate. The reference below is generated from the Berlin Group **openFinance API Framework — Extended Account Information Services, version 2.2**. The four account families it adds — cards, savings, loans and securities — are exactly the products PSD2 leaves out. ## Cards {% openapi src="" path="/cards" method="get" %} {% endopenapi %} {% openapi src="" path="/cards/{card-id}" method="get" %} {% endopenapi %} {% openapi src="" path="/cards/{card-id}/balances" method="get" %} {% endopenapi %} {% openapi src="" path="/cards/{card-id}/transactions" method="get" %} {% endopenapi %} ## Savings accounts {% openapi src="" path="/savings" method="get" %} {% endopenapi %} {% openapi src="" path="/savings/{account-id}" method="get" %} {% endopenapi %} {% openapi src="" path="/savings/{account-id}/balances" method="get" %} {% endopenapi %} {% openapi src="" path="/savings/{account-id}/transactions" method="get" %} {% endopenapi %} ## Loan accounts {% openapi src="" path="/loans" method="get" %} {% endopenapi %} {% openapi src="" path="/loans/{account-id}" method="get" %} {% endopenapi %} {% openapi src="" path="/loans/{account-id}/balances" method="get" %} {% endopenapi %} {% openapi src="" path="/loans/{account-id}/transactions" method="get" %} {% endopenapi %} ## Securities accounts {% openapi src="" path="/securities-accounts" method="get" %} {% endopenapi %} {% openapi src="" path="/securities-accounts/{account-id}" method="get" %} {% endopenapi %} {% openapi src="" path="/securities-accounts/{account-id}/positions" method="get" %} {% endopenapi %} {% openapi src="" path="/securities-accounts/{account-id}/transactions" method="get" %} {% endopenapi %} {% openapi src="" path="/securities-accounts/{account-id}/transactions/{transactionId}" method="get" %} {% endopenapi %} {% openapi src="" path="/securities-accounts/{account-id}/orders" method="get" %} {% endopenapi %} {% openapi src="" path="/securities-accounts/{account-id}/orders/{orderId}" method="get" %} {% endopenapi %} ## Statements {% openapi src="" path="/accounts/{account-id}/statements" method="get" %} {% endopenapi %} {% openapi src="" path="/account-statements" method="get" %} {% endopenapi %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.api.tieto.com/api-references/openfinance/extended-account-information-service.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.