> 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/obl-standard/account-and-transaction-api.md). # Account and Transaction API The UK equivalent of regulated account access: a licensed third party reads a bank customer's accounts, balances, transaction history and standing data — beneficiaries, direct debits, standing orders, scheduled payments and statements — once the customer has agreed to it. It is what UK budgeting, accounting, affordability and credit-decisioning products are built on. Your platform publishes it for each tenant bank, satisfying the account-access side of their UK obligations in the form UK providers already integrate with, and giving those providers one connection instead of one per bank. Access is limited to what the customer agreed and lasts only as long as they agreed it, and every call is recorded across the tenant base — which is what makes both supervisory reporting and a customer's own question about who saw their data answerable. {% hint style="info" %} The platform serves account access consents, accounts, balances, transactions, beneficiaries, direct debits, standing orders, scheduled payments, parties and statements. The standard's product, offer and cross-account bulk resources are part of the specification but not in the current platform scope. {% endhint %} ## Account access consents {% openapi src="" path="/account-access-consents" method="post" %} {% endopenapi %} {% openapi src="" path="/account-access-consents/{ConsentId}" method="get" %} {% endopenapi %} {% openapi src="" path="/account-access-consents/{ConsentId}" method="delete" %} {% endopenapi %} ## Accounts {% openapi src="" path="/accounts" method="get" %} {% endopenapi %} {% openapi src="" path="/accounts/{AccountId}" method="get" %} {% endopenapi %} ## Balances and transactions {% openapi src="" path="/accounts/{AccountId}/balances" method="get" %} {% endopenapi %} {% openapi src="" path="/accounts/{AccountId}/transactions" method="get" %} {% endopenapi %} ## Standing data {% openapi src="" path="/accounts/{AccountId}/beneficiaries" method="get" %} {% endopenapi %} {% openapi src="" path="/accounts/{AccountId}/direct-debits" method="get" %} {% endopenapi %} {% openapi src="" path="/accounts/{AccountId}/standing-orders" method="get" %} {% endopenapi %} {% openapi src="" path="/accounts/{AccountId}/scheduled-payments" method="get" %} {% endopenapi %} {% openapi src="" path="/accounts/{AccountId}/parties" method="get" %} {% endopenapi %} {% openapi src="" path="/accounts/{AccountId}/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/obl-standard/account-and-transaction-api.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.