About 4 weeks ago, I had the opportunity to take part in a FinTech hackathon in Tel Aviv. Bank Leumi, one of the largest banks in Israel, was organizing the event and Salesforce was sponsoring it. The event was awesome and vibrant. You had plenty of opportunities to meet some clever and creative people and learn about the latest trends in FinTech.
Salesforce was not the only sponsor. There were plenty more, with interesting products to use as part of your hacks. Some companies that were offering their products to use during the event were: Yodlee, import.io, TheThings.io, Built.io, Mashery, OpenBankProject and many more.
There is a clear trend for FinTech startups. Anyone who deals with a bank and some more advanced operations, may understand why this space is ideal for disruption. Although I wouldn’t call myself an expert into FinTech, I enjoyed what I learned during the event, which was a lot. I am even happier as I had the opportunity to get some useful insights about another technology topic that I love, APIs. FinTech is about data, as such, the majority of the products you could work with during the event, were exposing an API.
This is what this post is all about, “APIs and Hackathons”. I want to discuss about things that I saw worked or not and share some personal thoughts about APIs in general. Especially for public APIs exposed to developers and external services.