Nbg Gr Account and Transaction API Specification - UK

Name: Account and Transaction API Specification - UK API
Brand: Account and Transaction API Specification - UK
Availability: InStock

Browse all Nbg Gr APIs

★ Only Publicly Available OpenAPI DocumentFinanceBankingoauth2, apiKey21 Endpoints

Install Jentic One Beta

Connect the Account and Transaction API Specification - UK to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Account and Transaction API Specification - UK, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Account and Transaction API Specification - UK API.

Create, retrieve, and revoke account access consents under the UK Open Banking v3.1.5 model

List the customer's NBG accounts and read individual account metadata

Read balances, transactions, and statement detail for a chosen account

GET STARTED

Start building with Account and Transaction API Specification - UK API

Explore with Jentic

View OpenAPI Document

For Agents

Read NBG accounts, balances, transactions, statements, standing orders, and beneficiaries through a UK Open Banking v3.1.5 AISP interface.

Use for: Create an account access consent for an NBG customer, List all accounts authorised under a consent, Get the current balances for an NBG account, Retrieve transactions for a specific NBG account and date range

Not supported: Does not handle payment initiation, card issuing, or loan origination - use for UK Open Banking AISP read access to NBG accounts, balances, transactions, statements, and sandbox provisioning only.

Use Cases

Patterns agents use Account and Transaction API Specification - UK API for, with concrete tasks.

★ AISP Account Aggregation for NBG Customers

Account information service providers offering personal finance dashboards need a UK Open Banking compliant feed for NBG customer accounts. The API's account, balance, and transaction endpoints, gated by /account-access-consents, return the data required to populate a dashboard once consent is granted. The flow follows the UK Open Banking v3.1.5 profile so existing AISP code paths can be reused.

POST /account-access-consents to obtain a consent ID, then call /accounts and /accounts/{accountId}/transactions for each authorised account.

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.

Pull /accounts/{accountId}/balances and /accounts/{accountId}/transactions every 12 hours for each authorised NBG account and update the PFM database.

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.

List statements via /accounts/{accountId}/statements, then for each statement call /accounts/{accountId}/statements/{statementId}/file to download the PDF.

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.

POST /sandbox with a fresh dataset payload at the start of a test run, then DELETE /sandbox/{sandboxId} once the suite finishes.

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.

Search Jentic for 'list account balances under an Open Banking consent', load the schema for /accounts/{accountId}/balances, and execute it for the user's authorised NBG account.

Key Endpoints

21 endpoints — this nbg main spec is the canonical catalogue entry for the national bank of greece account and transaction api, implementing the uk open banking account and transaction profile v3.

METHOD

PATH

DESCRIPTION

POST

/account-access-consents

Create an account access consent

GET

/account-access-consents/{consentId}

Retrieve an account access consent

DELETE

/account-access-consents/{consentId}

Revoke an account access consent

GET

/accounts

List authorised accounts

GET

/accounts/{accountId}/balances

Get balances for an account

GET

/accounts/{accountId}/transactions

List transactions for an account

GET

/accounts/{accountId}/standing-orders

List standing orders on an account

GET

/accounts/{accountId}/statements/{statementId}/file

Download a statement file

POST

/account-access-consents

Create an account access consent

GET

/account-access-consents/{consentId}

Retrieve an account access consent

DELETE

/account-access-consents/{consentId}

Revoke an account access consent

GET

/accounts

List authorised accounts

GET

/accounts/{accountId}/balances

Get balances for an account

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your NBG OAuth client credentials and Client-Id header value are stored once, encrypted, by your own Jentic One instance, which runs the token exchange and injects them at execution time. Raw bank or client secrets never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list NBG account transactions under an Open Banking consent', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Account and Transaction API Specification - UK API through Jentic.

What authentication does the NBG Account and Transaction API use?

The API requires OAuth 2.0 with both client-credentials and authorisation-code flows, plus a Client-Id header on each request. Jentic stores the OAuth client and Client-Id values in its vault and runs the token exchange transparently before the AISP call.

Can I list a customer's accounts and balances with the NBG Open Banking API?

Yes. After establishing a consent via POST /account-access-consents, GET /accounts returns the authorised accounts and GET /accounts/{accountId}/balances returns the current and available balance per account in the UK Open Banking v3.1.5 schema.

What are the rate limits for the NBG Open Banking API?

The OpenAPI spec does not publish numeric rate limits. UK Open Banking guidance limits AISP polling for unattended access to four calls per consent per 24 hours per resource and allows higher rates while the user is present; confirm exact NBG limits in the developer portal at developer.nbg.gr.

How do I read NBG transactions through Jentic?

Run pip install jentic, search for 'list NBG account transactions under an Open Banking consent', load the schema for /accounts/{accountId}/transactions, and execute it once Jentic has handled the consent and OAuth steps. Run it through Jentic One, the self-hosted execution layer.

Does this API let me initiate payments?

No. The Account and Transaction surface is read-only AISP. Initiating payments under UK Open Banking PISP requires a separate Payment Initiation API specification, which is not covered by this spec.

Can I provision sandbox data for testing the NBG API?

Yes. POST /sandbox creates a sandbox dataset, PUT /sandbox imports an existing dataset, GET /sandbox/{sandboxId} exports it, and DELETE /sandbox/{sandboxId} removes it. These endpoints let CI pipelines set up reproducible test state per run.

Can I limit what my agent is allowed to do with the NBG Open Banking API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. Since NBG puts the account id in the URL path, a rule can pin the agent to a single account so it only reads that account's balances, transactions, and statements. You choose the exact operations it may call, so revoking an account access consent stays off limits unless you explicitly grant it.

Nbg Gr Account and Transaction API Specification - UK

Connect the Account and Transaction API Specification - UK to your agent

Capabilities

Start building with Account and Transaction API Specification - UK API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs