Autogenerate Runscope-powered API SDKs Using APIMatic
01 Oct 2014
Swagger is now Open API Definition Format (OADF) -- READ MORE
As the API lifecycle continues to expand and comes into focus, new services are emerging to help both API providers, and consumers, better manage API operations from start to finish. New API integration services like Runscope have emerged to better understand how APIs are actually being consumed, and services like APIMatic are born out of the need to produce better quality SDKs for developers--it only seems natural that eventually these services would start working together.
APIMatic will now generate SDKs in 7 languages that are designed, and enabled to inspect/debug all of the requests and response data between their API, and the applications that depend on them. This will provide both API provider, and consumer with vital details on the integration in real-time, that can help ensure applications integrations are all optimized.
All of this is made possible because Runscope has APIs, and APIMatic was savvy enough to weave in integration, monitoring and testing capabilities directly into the SDKs of any API. APIMatic will import API definitions in WADL, Swagger, I/O Docs, API BluePrint, or Google Discovery, then generate SDKs for you in Android, Windows, iOS, Java, PHP, Python, Ruby, and Node.js, complete with Runscope integration, monitoring and testing! Something made possible because you have a machine readable API definition for all of your APIs.
This latest expansion of the API lifecycle I feel was kicked off by Swagger, introducing the ability to generate interactive docs, server and client code for your APIs. This was then expanded upon by Apiary.io by allowing you to mockup APIs using API Blueprint, and now APIMatic and Runscope are expanding the lifecycle to include SDKs and API monitoring. It makes me happy to see the API definition continue to play such an important role, as the central truth in the API lifecycle, enabling all of these API services along the way.
Someday I'll create a cool little lifecycle visualization that shows each step in an APIs life, and what is enabled by using a central, machine readable API definition for all of your APIs, and underlying data models, but we all know graphics isn’t one of my strengths, so we'll see..
Updated November 27, 2015: Links were updated as part of switch from Swagger to OADF (READ MORE)