A

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](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/profiles/account-and-transaction-api-profile.html) This Accou

Finance & Banking

About

## Functionality at a glance The NBG "UK OPB - Account and Transaction v3.1.5" API follows the [UK Open Banking Specification v3.1.5](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/profiles/account-and-transaction-api-profile.html) 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 forms (title and short description) 2. Check **\"Authorization Code\" and \"Client Credentials\"** 3. Enter the **OAuth Redirect and Post Logout URIs** (these are the URIs that we will redirect the user upon logging in and logging out respectively) You can use the following redirect URL to easily test the API through the portal: *https://developer.nbg.gr/oauth2/redoc-callback* 4. Click **"SUBMIT"** 5. Store the APPs **"Client ID"** and **"Client Secret"** 5. Go to **"API PRODUCTS"** and select the **ACCOUNT INFORMATION - UK OPEN BANKING API** 6. Click **\"START USING THIS API\"**, choose your app and click **"SUBSCRIBE"** 7. Get an Access Token using the Access Token Flow and the API scopes provided in the Authentication and Authorization (OAuth2) section below 8. Create a Sandbox 9. Play with the API ### Sandbox Flow The Sandbox Flow matches the Production Flow. The difference lies into the Data used. Instead of live data, the Sandbox flow uses mocked data. ### Production Flow The Production Flow is described in the [UK Open Banking v3.1.5 Specification](https://openbankinguk.github.io/read-write-api-site3/v3.1.5/profiles/account-and-transaction-api-profile.html) More details about the implementation specifics followed, please visit section **UK OPB Implementation Specifics** ## Authentication and Authorization (OAuth2) This API version uses the OAuth2 protocol for authentication and authorization, which means that a Bearer (access token) should be acquired. An access token can be retrieved using the client_id and client_secret of the APP that you created and subscribed in this API, and your own credentials (username, password) that you use to sign in the NBG Technology HUB. The scopes are defined below: **Authorization Endpoint:** https://my.nbg.gr/identity/connect/authorize **Token Endpoint:** https://my.nbg.gr/identity/connect/token ### Authorization Code ### **Sandbox Scopes:** sandbox-uk-account-info-api-v1 offline_access **Production Scopes:** accounts offline_access ### Client Credentials ### **Sandbox Scopes:** sandbox-uk-account-info-api-v1 **Production Scopes:** accounts See more [here](https://developer.nbg.gr/oauth-document) ## QWAC Certificates TPPs are required to present a QWAC certificate during API consumption. The API checks that this certificate has been provided and is valid. In sandbox mode the certificate validations are optional. To validate your certificate in sandbox implementation, please send us your QWAC certificate at [email protected] and set the HTTP Header **\"x-sandbox-qwac-certificate-check\"** with the value **\"true\"** in your requests. ## SMS Challenge (One Time Password) In order to successfully authorize an Accounts Access you will need to provide the SMS OTP (One Time Password) in the corresponding Accounts Consent UI Screen. By default the SMS OTP will be sent to the mobile number declared upon singing up in the NBG Technology HUB. ## Create your Sandbox Create a new Sandbox application by invoking the POST /sandbox. This call will generate a new Sandbox with a unique sandbox-id. __Important!__ Before proceeding save the sandbox id you just created. When you create a sandbox, users and sandbox specific data are generated as sample data. ## Start Testing Once you have your sandbox-id, you can start invoking the rest of the operations by providing the mandatory http header **sandbox-id** and the http headers described below. ## Important notes **Request headers** The following HTTP header parameters are required for every call: 1. Authorization. The Auth2 Token 2. sandbox-id. Your Sandbox ID **Consent** In order to be able to effectively start using the Endpoints the appropriate Cons

No reviews yet. Be the first to review!

Visit Website

developer.nbg.gr

Details

Added
Nov 20, 2026
Directory
API

API Details

API Type
REST
Spec Format
OpenAPI
Version
v3.1.5

Share this listing

Share: