Don’t Get Stranded on API Data Islands
#ICYDK: I’ve seen many API specifications varying across the board from SOAP to REST with random others in between. While you can typically sum up the components of an API spec into category types; such as web service, authentication, resources, methods, events, search, and so forth, they are never the same in terms of data payload definition. Every endpoint is different in how it expects to receive or return data from calls made via its API. It is its own API island with its own language, so to speak.
Point-To-Point
So, if you have a SaaS application or you are looking to sync data between endpoints, the traditional way that many iPaaS platforms solve the issue of inconsistent data structures is to provide simple wrappers, or “connectors” — which convert the data into a format that can be read by another connector that is designed to work with it. This, in the world of API integration, is referred to as point-to-point connectivity. This works well and has been the model used to connect endpoint services together for years. https://goo.gl/jXY4HK
