Account and Transaction API Specification - UK

Personal Finance Management Integration

PFM apps and accounting tools that connect to Greek bank accounts read balances and transactions on a regular schedule to keep budgets and spending insights current. /accounts/{accountId}/balances and /accounts/{accountId}/transactions return real-time balance and posted-transaction feeds in the standard UK Open Banking shape. Standing orders and scheduled payments help the PFM forecast upcoming cash flow.

Statement Retrieval for Lending and Underwriting

Lenders and underwriters use bank statements as primary evidence in affordability and KYC checks. /accounts/{accountId}/statements lists available statements, /accounts/{accountId}/statements/{statementId} returns metadata, and /accounts/{accountId}/statements/{statementId}/file downloads the statement document. Combining the three calls automates statement collection during a loan application.

Sandbox Provisioning for AISP Development

Developers integrating with the NBG Open Banking surface need predictable sandbox datasets to test edge cases. /sandbox supports POST to create, PUT to import, GET to export, and DELETE to clear test datasets, allowing CI pipelines to set up and tear down state per test run. This avoids drift from a shared sandbox account.

Agent-Driven Account Insights via Jentic

Agents that surface bank balances or recent transactions for users need to navigate the Open Banking consent flow and OAuth dance without holding tokens directly. Through Jentic the agent searches by intent, loads the schema for the account or transaction operation, and executes it once consent is established, while Jentic stores the OAuth client credentials and Client-Id header in the vault. The agent never sees raw bank credentials.