Can HumDay connect to NBG Account and Transaction Specification UK?

Yes. HumDay reads NBG Account and Transaction Specification UK's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 21 operations are documented.

Do I need to write code to automate NBG Account and Transaction Specification UK?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your NBG Account and Transaction Specification UK account.

What can HumDay do in NBG Account and Transaction Specification UK?

5 of the 21 documented operations change something in NBG Account and Transaction Specification UK, and 16 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my NBG Account and Transaction Specification UK account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to NBG Account and Transaction Specification UK is held behind that approval.

Automate NBG Account and Transaction Specification UK

HumDay reads NBG Account and Transaction Specification UK’s own published API description and derives 21 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What NBG Account and Transaction Specification UK is

## 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

API host: apis.nbg.gr

What HumDay can do in NBG Account and Transaction Specification UK

5 documented operations change something in NBG Account and Transaction Specification UK.

POSTCreate Sandbox/sandbox
POSTCreate Account Access Consents/account-access-consents
PUTImport Sandbox/sandbox
DELETEDelete Sandbox/sandbox/{sandboxId}
DELETEDelete Account Access Consents/account-access-consents/{consentId}

What HumDay can read from NBG Account and Transaction Specification UK

These are the operations a schedule or a trigger can watch.

GETGet Party/party
GETGet Accounts/accounts
GETGet Standing Orders/accounts/{accountId}/standing-orders
GETGet Scheduled Payments/accounts/{accountId}/scheduled-payments
GETExport Sandbox/sandbox/{sandboxId}
GETGet Accounts/accounts/{accountId}
GETGet Account Access Consents/account-access-consents/{consentId}
GETGet Party/accounts/{accountId}/party
GETGet Parties/accounts/{accountId}/parties
GETGet Balances/accounts/{accountId}/balances
GETGet Statements/accounts/{accountId}/statements
GETGet Transactions/accounts/{accountId}/transactions
GETGet Beneficiaries/accounts/{accountId}/beneficiaries
GETGet Statements/accounts/{accountId}/statements/{statementId}/file
GETGet Statements/accounts/{accountId}/statements/{statementId}
GETGet Transactions/accounts/{accountId}/statements/{statementId}/transactions

How automating NBG Account and Transaction Specification UK works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live NBG Account and Transaction Specification UK account.
Grant access, then go live. You approve the specific NBG Account and Transaction Specification UK operations it may use — and only those.

Popular NBG Account and Transaction Specification UK integrations

Connect NBG Account and Transaction Specification UK to the tools people pair it with most.