Automate OpenFinTech.io
HumDay reads OpenFinTech.io’s own published API description and derives 18 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 OpenFinTech.io is
# Introduction [OpenFinTech.io](https://openfintech.io) is an open database that comprises of standardized primary data for FinTech industry. It contains such information as geolocation data (countries, cities, regions), organizations, currencies (national, digital, virtual, crypto), banks, digital exchangers, payment providers (PSP), payment methods, etc. It is created for communication o
API host: api.openfintech.io
What HumDay can read from OpenFinTech.io
These are the operations a schedule or a trigger can watch.
- GETList of payment methods
/payment-methods - GETList of payment providers
/payment-providers - GETList of banks
/banks - GETList of countries
/countries - GETList of currencies
/currencies - GETList of exchangers
/exchangers - GETList of organizations
/organizations - GETList of deposit methods
/deposit-methods - GETList of merchant industries
/merchant-industries - GETPayment method by ID
/payment-methods/{id} - GETPayment provider by ID
/payment-providers/{id} - GETBank by ID
/banks/{id} - GETCountry by ID
/countries/{id} - GETCurrency by ID
/currencies/{id} - GETExchanger by ID
/exchangers/{id} - GETOrganization by ID
/organizations/{id} - GETDeposit method by ID
/deposit-methods/{id} - GETMerchant industry by ID
/merchant-industries/{id}
How automating OpenFinTech.io 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 OpenFinTech.io account.
- Grant access, then go live. You approve the specific OpenFinTech.io operations it may use — and only those.
Automate OpenFinTech.io with these
- Stripe442 operations
- Zuora Reference Billing428 operations
- bunq421 operations
- PayRun.IO389 operations
- Sinao272 operations
- Xero Accounting224 operations
- The Plaid191 operations
- Biapi Budgea Documentation167 operations
- Naviplancentral Advicent.FactFinderService151 operations
- Bigredcloud Big Red Cloud111 operations
- Codat Accounting105 operations
- Portfoliooptimizer Portfolio Optimizer83 operations
Categories
Questions about OpenFinTech.io automation
- Can HumDay connect to OpenFinTech.io?
- Yes. HumDay reads OpenFinTech.io's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 18 operations are documented.
- Do I need to write code to automate OpenFinTech.io?
- 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 OpenFinTech.io account.
- What can HumDay do in OpenFinTech.io?
- 0 of the 18 documented operations change something in OpenFinTech.io, and 18 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my OpenFinTech.io 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 OpenFinTech.io is held behind that approval.
Where this came from
The operations above are read from a published API description for OpenFinTech.io at docs.openfintech.io/swagger.yaml. Descriptions are the provider’s own words, not ours. Last published 2018-04-19.