Automate Openbanking Confirmation of Funds Specification
HumDay reads Openbanking Confirmation of Funds Specification’s own published API description and derives 4 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 Confirmation of Funds Specification is
Swagger for Confirmation of Funds API Specification
API host: openbanking.org.uk
What HumDay can do in Openbanking Confirmation of Funds Specification
3 documented operations change something in Openbanking Confirmation of Funds Specification.
- POSTCreate Funds Confirmation
/funds-confirmations - POSTCreate Funds Confirmation Consent
/funds-confirmation-consents - DELETEDelete Funds Confirmation Consent
/funds-confirmation-consents/{ConsentId}
What HumDay can read from Openbanking Confirmation of Funds Specification
These are the operations a schedule or a trigger can watch.
- GETGet Funds Confirmation Consent
/funds-confirmation-consents/{ConsentId}
How automating Openbanking Confirmation of Funds 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 Confirmation of Funds Specification account.
- Grant access, then go live. You approve the specific Openbanking Confirmation of Funds Specification operations it may use — and only those.
Automate Openbanking Confirmation of Funds Specification with these
- Openbanking Account and Transaction Specification29 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 Confirmation of Funds Specification automation
- Can HumDay connect to Openbanking Confirmation of Funds Specification?
- Yes. HumDay reads Openbanking Confirmation of Funds Specification's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 4 operations are documented.
- Do I need to write code to automate Openbanking Confirmation of Funds 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 Confirmation of Funds Specification account.
- What can HumDay do in Openbanking Confirmation of Funds Specification?
- 3 of the 4 documented operations change something in Openbanking Confirmation of Funds Specification, and 1 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Openbanking Confirmation of Funds 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 Confirmation of Funds Specification is held behind that approval.
Where this came from
The operations above are read from a published API description for Openbanking Confirmation of Funds Specification at raw.githubusercontent.com/OpenBankingUK/read-write-api-specs/master/dist/openapi/confirmat. Descriptions are the provider’s own words, not ours. Last published 2021-03-07.