<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=184105&amp;fmt=gif">


The Latest News, Events and Product Resources for End Users

Working With APIs: DIY or Use a Trusted Integrator?

Posted by Kit Dickinson on Aug 11, 2016 7:42:12 AM
Kit Dickinson
Find me on:

Building a Bridge

APIs (application program interfaces) allow different systems to communicate with each other. APIs are an alternative to using files such as .txt or .csv, XML or database connections for data transfer. Many HCM vendors are opening up APIs or web services to allow clients or vendors to exchange information with their modules. However, a common misperception is that APIs complete the data exchange between different systems. We often hear the incorrect phrase “we have an API for that system” when discussing how two systems connect with each other.

Making the API Data Connection

The purpose of an API is to either expose information to be retrieved or provide standards for inserting data. APIs themselves don’t provide any mappings, business logic or other data transformation to move the data from one system to another. To make the actual data connection, one of three things needs to occur:

  1. The source or destination vendor creates a module or program in their system to work with the other vendor’s API.
  2. The client develops and maintains a program (middleware) to allow the two systems to exchange data.
  3. The client engages with an application integration company to provide a solution that manages the data transfer and any additional business logic so the systems reliably exchange data.

Because vendors generally focus on their core solution and expose APIs to allow others to connect with their systems (option 1), options 2 and 3 are the most common alternatives when it comes to data integration.

If you’re thinking about placing the data integration burden on your client, be sure to ask the following questions:

  1. Does the client have strong IT staff that can dedicate the time required to:
    • Learn your system’s APIs?
    • Learn the connecting system’s APIs?
    • Program and test the connection and any company-specific logic (e.g., custom calculations, allocating hours/earnings data, etc.)?
  2. Does the client have flexibility with their IT staff to support the connection through upgrades to either system or when data transfer errors occur?
  3. How much time will it take for the internal team to develop the data transfer program?
  4. What is your contingency plan if the client's IT staff has competing priorities and can’t complete the programming (thus jeopardizing your start date and billing)?

Experience Counts in API Integrations

Often, using an experienced application integration company is most appealing for everyone. IDI is based around providing reliable and cost-effective integrations using APIs or other transfer methods. IDI has been using vendors’ APIs for several years with our Time Bank™ solution. Time Bank has been used by more than 25,000 companies over the last 20+ years. Our team works with our partners’ implementation teams and clients to deliver the integration solutions on-time without burdening the client’s valuable internal resources with new development and ongoing support.

We’re often asked, “Couldn’t we just do this integration work?” The easy answer is “Yes.” However, the more strategic question is, “Should we be investing in this development and support?” Most companies we work with are satisfied that they utilized a proven company like IDI so they can stay focused on their business.

Professional Services Video


Learn More About Time Bank Solutions

Topics: Non Industry-Specific Solutions