Awesome APIs make for even better integrations, but like the APIs they connect, integrations can be unique and vary wildly. Yet, integration is becoming necessary, as many customer experiences are driven by aggregating existing data from applications instead of recreating it. Often times, creating enhanced views can speed up decision making by having your data available in one place. Integrations optimize processes by automating the transfer of data from one application to another or multiple applications, serving not only internal departments, but also customers, prospects, and partners.
The number of applications organizations use to conduct business on a daily basis is not only staggering but also increasing year over year. To use an example, there are now over 7,000 marketing applications to choose from that are being tracked by chiefmartec.com. Now think about all the applications engineering, product, QA, finance, accounting, and support use! Each of these applications will likely have their own APIs and, further, they may have different styles of APIs such as REST, SOAP, SDK, etc. So how do you bring all the data hiding in these applications together?
This Refcard serves as a starting place for some best practices when approaching integration. We'll begin with documentation and understanding the target application's endpoints, before learning to implement authentication to gain access to the data you need. Next, we'll cover eventing APIs and bringing that data to life by creating flows between applications. We will discover how to query for just the data we need, and finally, cover paging through those vast troves of data and moving it in bulk if need be.