Automate Openbanking Account and Transaction Specification
HumDay reads Openbanking Account and Transaction Specification’s own published API description and derives 29 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 Account and Transaction Specification is
Swagger for Account and Transaction API Specification
API host: openbanking.org.uk
What HumDay can do in Openbanking Account and Transaction Specification
2 documented operations change something in Openbanking Account and Transaction Specification.
- POSTCreate Account Access Consents
/account-access-consents - DELETEDelete Account Access Consents
/account-access-consents/{ConsentId}
What HumDay can read from Openbanking Account and Transaction Specification
These are the operations a schedule or a trigger can watch.
- GETGet Standing Orders
/standing-orders - GETGet Scheduled Payments
/scheduled-payments - GETGet Parties
/party - GETGet Offers
/offers - GETGet Accounts
/accounts - GETGet Balances
/balances - GETGet Products
/products - GETGet Statements
/statements - GETGet Transactions
/transactions - GETGet Beneficiaries
/beneficiaries - GETGet Direct Debits
/direct-debits - GETGet Standing Orders
/accounts/{AccountId}/standing-orders - GETGet Scheduled Payments
/accounts/{AccountId}/scheduled-payments - GETGet Accounts
/accounts/{AccountId} - GETGet Account Access Consents
/account-access-consents/{ConsentId} - GETGet Parties
/accounts/{AccountId}/party - GETGet Offers
/accounts/{AccountId}/offers - GETGet Parties
/accounts/{AccountId}/parties - GETGet Products
/accounts/{AccountId}/product - GETGet Balances
/accounts/{AccountId}/balances - GETGet Statements
/accounts/{AccountId}/statements - GETGet Transactions
/accounts/{AccountId}/transactions - GETGet Beneficiaries
/accounts/{AccountId}/beneficiaries - GETGet Direct Debits
/accounts/{AccountId}/direct-debits - GETGet Statements
/accounts/{AccountId}/statements/{StatementId}/file - GETGet Statements
/accounts/{AccountId}/statements/{StatementId} - GETGet Transactions
/accounts/{AccountId}/statements/{StatementId}/transactions
How automating Openbanking Account and Transaction Specification 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 Account and Transaction Specification account.
- Grant access, then go live. You approve the specific Openbanking Account and Transaction Specification operations it may use — and only those.
Automate Openbanking Account and Transaction Specification with these
- Openbanking Confirmation of Funds Specification4 operations
- Openbanking Event Notification Specification TPP Endpoints1 operations
- Openbanking Open Data6 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 Account and Transaction Specification automation
- Can HumDay connect to Openbanking Account and Transaction Specification?
- Yes. HumDay reads Openbanking Account and Transaction Specification's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 29 operations are documented.
- Do I need to write code to automate Openbanking Account and Transaction Specification?
- 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 Account and Transaction Specification account.
- What can HumDay do in Openbanking Account and Transaction Specification?
- 2 of the 29 documented operations change something in Openbanking Account and Transaction Specification, and 27 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Openbanking Account and Transaction Specification 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 Account and Transaction Specification is held behind that approval.
Where this came from
The operations above are read from a published API description for Openbanking Account and Transaction Specification at raw.githubusercontent.com/OpenBankingUK/read-write-api-specs/master/dist/openapi/account-i. Descriptions are the provider’s own words, not ours. Last published 2021-03-07.