API Providers Can Create, Preview and Edit Swagger Specs with Latest Tools, and API Developers Can Explore APIs Live From Provider Documentation
We use Swagger to help our customers offer better and easier to understand interactive API documentation for their users with ActiveDocs. And by integrating Swagger into our product’s developer portal we help make the experience simple, fast and delightful for API consumers. We were onboard with Swagger from the start and continue to support and contribute to the standard. We’re pretty excited about announcing this at Gluecon today.
Specifically, 3scale’s API provider customers can use ActiveDocs to create, preview and edit API specifications using the latest version of the Swagger user interface. Developers can also use ActiveDocs to make test calls against provider APIs and get details on cURL commands needed for testing as well as operations groupings, and support for complex data types including hash, array and custom.
Developers can also see which ActiveD…
Flexibility, scalability and security are probably the main keywords we tried to keep in mind during the API development.
Interview with Vivien Genet, Senior Developer at Jamendo.
Tell us more about the development process of the Jamendo API
When we decided to redesign Jamendo, we quickly thought that the API should be a priority in our planning: first, because it is THE main way for Jamendo to live outside www.jamendo.com (on social networks, mobiles, etc.), and second, because the migration of existing applications (based on our previous API) will take some time.
To develop the new API, we have used the Zend framework (as for the website) but we made a sub-framework specifically for the API to make it easier to change.
The current online version is the beta version. Developers who hav…
We did not set out to create an API. We initially developed Convey as an internal library for use in Converseon’s products and service.”
Interview with Mark Walz VP Product Management at Converseon. You can follow Mark on twitter: @rocketmark
Tell us about the development process of the Convey API
We did not set out to create an API. We initially developed Convey as an internal library for use in Converseon’s products and service. The Convey library has been several years in the making and has involved industry and academic expertise from its inception.
As Convey’s power and accuracy grew, we began to see applications for it outside of our own products and so did our clients. As received inquiries and proposal requests for large volume text analytics, we decided to take the Convey library and make it availab…