Independent API management vendors seem to be a bit redundant these days, with organizations now viewing API management as an extension of integration platforms.
The previously crowded field of pure play API management vendors has been thinned out as a result. A flurry of recent acquisitions of major API management vendors, such as Tibco’s purchase of Mashery, Google’s purchase of Apigee, and Rogue Wave Software’s Akana buy, showed the world that APIs are part of a bigger market.
For example, with open banking initiatives such as the Payment Services Directive 2 (PSD2) in Europe and the Competition and Markets Authority’s (CMA) in the UK, it is imperative that banks open up their banking data to third party payment providers and account aggregators in 2018. That not only means securely providing this banking data to third parties via APIs. It also means accessing the data within systems, structuring it to meet regulatory and industry requirements, and packaging it as a set of services that provide the work behind the APIs.
That’s why it makes sense to consider API management as an extension of integration —because it’s within integration technologies that many organizations are defining the data structures and building out services that they are exposing as APIs. Accessing the right data and defining the backend services is the hard part. Exposing the APIs is an extension of that process.
You don’t need a middleman between your APIs and your integration platform. Integration technologies and API Management technologies are now fully integrated. We’ve integrated integration.