Integrate good times, come on ūü§Ě

I read somewhere that the average company uses 100+ SaaS apps. Regardless of the specific number, it’s a lot. Like water molecules traveling through¬†trees, rivers, and animals, pieces of data flow through these SaaS apps, powered by integrations. As users, we’ve gotten use to these integrations, but they take time to build.

This is where integration aggregators like¬†Plaid¬†come in. If you’re building a fintech startup, connect with the Plaid API and “boom!” your users can connect with 1000 banks. Think about the downstream impact of this on the fintech ecosystem.

Finch¬†is a universal API for payroll and HR.¬†Noyo¬†is for connecting with insurance APIs. Use the¬†Wearable API¬†to connect with 300+ fitness devices and apps.¬†Impala‘s API to book hotel rooms and¬†Duffel¬†to sell flights in your app.¬†Rutter¬†is an API to connect with e-commerce platforms.¬†Seam¬†has an API to connect with 1000s of smart home/building apps and devices (for hotels &¬†apartments).¬†API Deck¬†is a unified API for SaaS apps to launch integrations faster with each other.¬†Paragon¬†is a dev solution for integrating your product w third party SaaS apps.

Even with integrations, a user may want to run more complex automation flows. That’s when they’ll use¬†Zapier¬†(I ran 1557 tasks this last month),¬†Tray¬†(if you do lots of branching), or¬†Parabola¬†(if you run loops).

Beyond aggregators & automators, here’s a few more¬†APIs¬†that recently¬†peak my interest.¬†Check¬†and¬†Puzzl¬†help devs integrated payroll into their platforms.¬†Eligible¬†is for integrated insurance billing into a health startup.¬†Patch¬†is an API for managing climate impact.¬†Mesh¬†is for verifying professional licenses.¬†Appruve¬†is an identity API for Africa.






Leave a Reply

Your email address will not be published. Required fields are marked *