Earlier I wrote about what an API (Application Programming Interface) is and its purpose. Today, I will describe two recent API projects as examples of the capabilities possible due to the existence of API’s.
When using a Constituent Relationship Management (CRM) database you want to track all communication with each constituent in addition to their name, contact information, donation, pledges, and meeting, etc. One of the most frequently used communication tools is email. Some databases have the capability to send emails directly and store a copy in the constituent record. Some do not. Many people use an online email provider that is not integrated with their CRM. So how do you get the emails into the CRM database? Develop an API app.
eComApps recently created a process to receive emails, identify the various parts of the email, and then find the appropriate account within the CRM database and add the email content. All the user has to do is include a special email address when sending the email. Everything else is automatic. The API allows us to write code to access the CRM, find the proper record, and add the email content. Yes, this is the eCom-EmailKeeper product recently released.
Another recent project involved a ticketing system and a CRM database each with their own API. Our API app accesses the ticketing database, pulls out the appropriate event transactions, identifies those that have not been previously processed, and then accesses the CRM to find the appropriate records and add the transactions. Our app uses the ticketing database API to obtain the records and the CRM API to move the data into the appropriate CRM records. This is a custom solution for one of our clients.
API technology gives you the ability to customize a complex process to meet specific needs. It saves time, is easy to use, and makes your life easier. Sweet!