Skip to content
Banking/open banking

nbg.gr

Account and Transaction API Specification - UK sandbox and mock API

## 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 Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
21
Collections
-
Event types
-
example request
curl https://your-nbg-gr.slurry.io/sandbox/uk.openbanking.accountinfo/oauth2/v3.1.5/accounts \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version v3.1.5.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 21.

  • POST/account-access-consents
  • GET/account-access-consents/{consentId}
  • DELETE/account-access-consents/{consentId}
  • GET/accounts
  • GET/accounts/{accountId}
  • GET/accounts/{accountId}/balances
  • GET/accounts/{accountId}/beneficiaries
  • GET/accounts/{accountId}/parties
  • GET/accounts/{accountId}/party
  • GET/accounts/{accountId}/scheduled-payments
  • GET/accounts/{accountId}/standing-orders
  • GET/accounts/{accountId}/statements