Swagger 2.0 spec was created with the foresight of allowing 3rd-party vendors to implement tool specific extensions. These extensions allow customizing behaviors beyond simple API descriptions. Traditionally, such behaviors used to stay locked inside custom settings, restricting interoperability of tools and services. Using these extensions, we can not only offer extended compatibility between tools and services, but this also opens up a pathway to improve and add missing features that eventually becomede-facto standard for API descriptions. For example, extensions that allow customization of API analytics data collections e.g., how to treat rate limit exceeded, may eventually become part of official Swagger spec if the developer community decide in its favor. One widely known example of Swagger vendor extension is the Apigee a-127 extension, which allows you to generate APIs in Node.js. API Evangelist has already written a post about this concept some while ago (read it here).
Tag Archives: Swagger
Swagger is a simple yet powerful representation of your RESTful API. With the largest ecosystem of API tooling on the planet, thousands of developers are supporting Swagger in almost every modern programming language and deployment environment.
With a Swagger-enabled API, you get interactive documentation, client SDK generation and discoverability.
Why is Node.js a good choice for building APIs? What is Swagger 2.0 and how can you use it to create your API documentation?
Join Jeff West and Marsh Gardiner for a code and demo-filled session, in which we’ll design an API with Swagger 2.0 and then implement and deploy the API in Node.js on both Apigee and AWS.
We will ‘show the code’ to:
• Build production-grade APIs in Node.js with Apigee-127
• Create API documentation with Swagger 2.0
• Add enterprise capabilities like OAuth, quota, caching, and analytics using NPMs (Node Package Manager)
• Deploy to any PaaS, including Apigee, Amazon AWS, and Heroku
Download slides: slidesha.re/1tgR1eK
Download podcast: https://soundcloud.com/apigee/build-a…
Swagger has become the standard for defining APIs in JSON with a huge community and a diverse set of tools. Apigee began to contribute to the tooling during the working group’s definition of the 2.0 of Swagger specification. We embraced JSON Schema for validation and particularly invested in the API design-first workflows that a YAML-based format for editing enables.
An example project for Apigee-127, an open source framework for building APIs in Node.js and Swagger 2.0.
This example shows an API consuming another API
The Swagger 2.0 specification was officially released today and at StrongLoop we are excited to announce that LoopBack is the first Node.js framework to support Swagger 2.0. Using LoopBack you can now take a Swagger 1.2 or 2.0 specification and automatically scaffold a Node-powered REST API. This should be especially useful for any developer wanting to easily describe their APIs using the leading enterprise standard for API specification and implement them in Node.js. Developers now have the ultimate flexibility in starting from a “bottoms up” approach – building APIs from existing data sources or a “top down” approach – starting with the leading enterprise API specification and scaffolding up a backend of generated models.