API archive entry · source-reported
Account and Transaction API Specification - UK
## Functionality at a glance The NBG "UK OPB - Account and Transaction v3.1.5" API follows the UK Open Banking Specification v3.1.5 This Account and Transaction API Specification describes the flows and payloads for retrieving a list of accounts and their transactions. The API endpoints described here allow a AISP to: * Create the Consent with the appropriate permissions in order to be able to access the API Endpoints * Retrieve the list of accounts * Retrieve an account's details * Retrieve an account's balances * Retrieve an account's transactions * Retrieve an account's beneficiaries * Retrieve an account's standing orders * Retrieve an account's party * Retrieve an account's scheduled payments * Retrieve an account's statements ## Quick Getting Started 1. **Login/Register** to the NBG Technology HUB 2. Go to **"APPS"** 3. Select your Organization and go to step 4. If you want to create a new Organization click **\"CREATE AN ORGANIZATION\"** and follow the steps below: 1. Enter the title of your Organization 2. Enter a short description of your Organization (optional) 3. Click **"SUBMIT"** 4. Select the Organization of choice and click **"ADD AN APPLICATION"** 1. Fill in the for
Plan the first integration safely
The access fields below come from the connected directory. Their likely implementation impact is explained without assuming provider-specific behavior.
Authentication
OAuth is reported. Confirm flows, scopes, consent, token lifetime, and refresh rules.
Transport
HTTPS is not confirmed. Do not send credentials or production data until secure transport is verified.
Browser access
CORS is unknown. Treat direct browser access as unconfirmed and test before choosing a client-only architecture.
First-request sequence
- Identify the current base URL, version, and endpoint for the use case.
- Confirm how credentials are issued and where they may be stored.
- Test success, invalid input, throttling, unavailable data, and timeouts.
- Record response fields, pagination, caching, and error shapes.
- Add monitoring, retries with backoff, and an appropriate fallback.
Questions to resolve before production
Pricing and quotas
Confirm current plans, free-tier limits, overages, and request ceilings.
Endpoint coverage
Check that the operations and response fields match the intended workload.
Reliability
Look for uptime history, a status page, support routes, and service commitments.
Data and privacy
Review retention, licensing, regional processing, and compliance requirements.
Versioning
Confirm the active version, change policy, deprecation window, and migration guidance.
Developer experience
Validate SDKs, examples, error formats, pagination, and test environments.
Source reference
This page separates source-reported facts from questions that need live provider verification.