Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

It's Easier to Offer Ops APIs to Your Devs If Your API Service Provider Has APIs

DZone's Guide to

It's Easier to Offer Ops APIs to Your Devs If Your API Service Provider Has APIs

API providers are increasingly offering ops level APIs to devs, thus affording them better control over integration. Check out how this trend has evolved, and why offering these APIs to devs is simpler if your service provider has APIs.

· Integration Zone
Free Resource

Today’s data climate is fast-paced and it’s not slowing down. Here’s why your current integration solution is not enough. Brought to you in partnership with Liaison Technologies.

I'm looking at the pricing APIs offered by some of the API providers that are further along in their API journey. This is just one example of how API providers are offering more operational level APIs to their developers, giving them control over their own integration, allowing programmatic control over account settings, billing, rate limits, and pricing.

I've talked about the need to allow for more automation of the modern API life cycle, allowing API consumers to better manage their consumption across the many APIs they are depending on. This is why I'm spending a greater amount of time focusing on API service providers in the space practicing what they preach, and making simple, easy to use APIs available for the services they offer.

When API service providers do this, it make it easier for API providers to extend API driven operations to their consumers. The fact that my 3Scale API management infrastructure has an API, allows me to proxy and deliver a pricing, plans, and rate limit API to my API consumers. All of these elements are present in the service composition 3Scale provides me, and the fact that they have an API allows me to extend it as part of my own API stack to my consumers.

This does not stop with just the API management line of my API life cycle. I can provide programmatic access to my API monitoring, because API Science andRunscope has APIs, and to my SDKs via APIMATIC, and multi-format versions of my API definitions using the API Transformer API. Every stop along my API life cycle involves my API consumers, and in addition to me being able to automate my API operations using APIs, my developers should be able to automate their API consumption as well.

The moral of this story I guess, is that if you are providing services to API providers--have all of your services available via an API. Once you have done this, start thinking about how your customers will be needing to extend these services to their own consumers. Thank you for helping me understand and manage my API operations, but also assist me in helping my developers better manage their own API integration--using APIs. #thanks

Is iPaaS solving the right problems? Not knowing the fundamental difference between iPaaS and iPaaS+ could cost you down the road. Brought to you in partnership with Liaison Technologies.

Topics:
api ,integration ,ei ,enterprise integration ,devops

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}