API Spotlight: Cloudifier, Gnip and Pactas APIs

Of the many APIs we published this week, seven were highlighted on the blog by our team of writers. In this post, we’ll illuminate those seven by throwing them into the spotlight. The eight included the Cloudifier API. Cloudifier allows users to create web applications without writing all the code. Instead they use the Cloudifier business programing language to create a solution, which Cloudifier then generates into a web application.  All of the Cloudifier functionalities are attainable through the Cloudifier API, giving developers the same power to create applications as normal users. To learn more about the Cloudifier API visit the Cloudifier site as well as the Cloudifier API blog post.

Travel agents should rejoice at the news of the iZento API. The iZento API takes XML data from providers and outputs a complete travel itinerary with guides, maps, calendars, and even recommended activities. Furthermore, it allows users to access their itineraries via mobile device; share their itinerary locations on Facebook to update their friends on their journey, and the ability to access the itinerary 30 days after their return home.  Users of iZento also receive a journal option, where they can upload their photos, write, print, and even order it from iZento if they want. To learn more about the iZento API visit the iZento site as well as the iZento API blog post.

Gnip is one of a select few companies that have full access to twitters data. With this access comes the Gnip Search API for twitter. Current search allows users to concatenate data in real time, but deeper analysis is reserved to those who have full access. Gnip effectively lets those who don’t have complete access, and that have enterprise access, to tweets ranging 30 days into the past. Gnip wanted to provide an extensive search service for historical tweets. This API, compared to Gnips old API, gives researchers more complex search functions into the past. To learn more about the Gnip API visit the Gnip site as well as the Gnip API blog post.

Social Foundry, API infrastructure provider, announced REST support for SOAPbox API. SOAPbox allows developers to expose their databases through a few lines of SQL operations. The idea is that users give SOAPbox their database connection information, write some SQL functions for their API, generate some API keys, and then let SOAPbox take care of the API management while the user continues development. SOAPbox simply sends API metrics to the developers dashboard along with any third party databases or files of their choosing. To learn more about the SOAPbox API visit the SOAPbox site as well as the SOAPbox API blog post.

PactasPactas is a recurring bill solutions provider. The Pactas API allows developers to leverage the Pactas functionality in their third party apps and websites. This German based company has optimized Pactas for the German market. All the data is held in Germany, the payment providers of choice are German, and the tariff models are intended to be used by German developers. Regardless, the billing service provides a much-needed remedy to the time consuming process of manually creating recurring payments.  To learn more about the Pactas API, visit the Pactas site as well as the Pactas API blog post.

Yodlee Interactive provides backend aggregation of over 12,000 financial data sources from over 100 different account types. The Yodlee API allows programmatic access to 99 percent of US financial accounts. Yodlee recently updated its API from being exlusively SOAP/XML based to supporting REST/ JSON and HTML. Yodlee wanted to provide developers with all the necessary things they would need in order to support cross- Platform and cross device development. Look for the 600 companies already using Yodlee to grow with this release. To learn more about the Yodlee API blog post visit the Yodlee site as well as the Yodlee API blog post.

CorePro API allows developers to integrate savings accounts into online and mobile applications. Through the platform companies are able to offer their customers FDIC insured savings accounts and fund transfers to and from the account. The API is currently in beta and will remain there until CorePro can be sure their API is sufficient. Functionality currently includes accruing and paying interest, generating monthly electronic statements, and electronic 1099 submission while maintaining SSAE 16 and PCI compliancy.  To learn more about the specific functionalities and how this is possible n the first place, visit the CorePro site as well as the CorePro API blog post.

Be sure to read the next API article: 56 New APIs: BuzzStream, Pactas and Panopta APIs