Automate Openbanking Open Data
HumDay reads Openbanking Open Data’s own published API description and derives 6 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 Openbanking Open Data is
Latest Swagger specification for OpenData
API host: developer.openbanking.org.uk
What HumDay can read from Openbanking Open Data
These are the operations a schedule or a trigger can watch.
- GETGets a list of all ATM objects.
/atms - GETGets a list of all Branch objects.
/branches - GETGets a list of all Unsercured SME Lending objects.
/unsecured-sme-loans - GETGets a list of all Commerical Credit Card objects.
/commercial-credit-cards - GETGets a list of all Branch Current Account objects.
/business-current-accounts - GETGets a list of all Personal Current Account objects.
/personal-current-accounts
How automating Openbanking Open Data 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 Openbanking Open Data account.
- Grant access, then go live. You approve the specific Openbanking Open Data operations it may use — and only those.
Automate Openbanking Open Data with these
- Openbanking Account and Transaction Specification29 operations
- Openbanking Confirmation of Funds Specification4 operations
- Openbanking Event Notification Specification TPP Endpoints1 operations
- Openbanking Payment Initiation41 operations
- Stripe442 operations
- Zuora Reference Billing428 operations
- bunq421 operations
- PayRun.IO389 operations
- Sinao272 operations
- Xero Accounting224 operations
- The Plaid191 operations
- Biapi Budgea Documentation167 operations
Categories
Questions about Openbanking Open Data automation
- Can HumDay connect to Openbanking Open Data?
- Yes. HumDay reads Openbanking Open Data's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 6 operations are documented.
- Do I need to write code to automate Openbanking Open Data?
- 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 Openbanking Open Data account.
- What can HumDay do in Openbanking Open Data?
- 0 of the 6 documented operations change something in Openbanking Open Data, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Openbanking Open Data 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 Openbanking Open Data is held behind that approval.
Where this came from
The operations above are read from a published API description for Openbanking Open Data at raw.githubusercontent.com/OpenBankingUK/opendata-api-spec-compiled/master/opendata-swagger. Descriptions are the provider’s own words, not ours. Last published 2020-11-23.