NSwag - The Swagger/OpenAPI toolchain for .NET, Web API and TypeScript.

•    CSharp

---

NSwag is a Swagger/OpenAPI 2.0 and 3.0 toolchain for .NET, .NET Core, Web API, ASP.NET Core, TypeScript (jQuery, AngularJS, Angular 2+, Aurelia, KnockoutJS, and more) and other platforms, written in C#. The Swagger specification uses JSON and JSON Schema to describe a RESTful web API. The NSwag project provides tools to generate Swagger specifications from existing ASP.NET Web API controllers and client code from these Swagger specifications. The project combines the functionality of Swashbuckle (Swagger generation) and AutoRest (client generation) in one toolchain. This way a lot of incompatibilites can be avoided and features which are not well described by the Swagger specification or JSON Schema are better supported (e.g. inheritance, enum and reference handling). The NSwag project heavily uses NJsonSchema for .NET for JSON Schema handling and C#/TypeScript class/interface generation.

nswag swagger openapi codegen webapi aspnetcore angular aurelia typescript

swagger-codegen - swagger-codegen contains a template-driven engine to generate documentation, API clients and server stubs in different languages by parsing your OpenAPI / Swagger definition

•    HTML

---

📔 The eBook A Beginner's Guide to Code Generation for REST APIs is a good starting point for beginners. Check out OpenAPI-Spec for additional information about the OpenAPI project.

swagger swagger-codegen rest rest-api openapi-specification

selling-partner-api-models - This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs

•    Java

---

This repository contains Swagger models for developers to use to create software to call Selling Partner APIs. Developers can use swagger codegen to generate client libraries from these models. Please refer to selling-partner-api-docs for additional documentation and read the Selling Partner Api Developer Guide for instructions to get started. The models directory contains all of the currently available Selling Partner API models.

spectacle - Beautiful static documentation generator for OpenAPI/Swagger 2.0

•    HTML

---

Spectacle generates beautiful static HTML5 documentation from OpenAPI/Swagger 2.0 API specifications. The goal of Spectacle is help you "save time and look good" by providing an extensible platform for auto generating your REST API docs. The default layout is a three column single page, similar to those employed by Stripe and Intercom.

openapi swagger docs documentation builder generator

ReDoc - 📘 OpenAPI/Swagger-generated API Reference Documentation

•    TypeScript

---

IMPORTANT NOTE: if you work with untrusted user spec, use untrusted-spec option to prevent XSS security risks.

openapi swagger api-documentation documentation-tool documentation-generator redoc reactjs openapi-specification json-schema api rest documentation react.js

swagger2markup - A Swagger to AsciiDoc or Markdown converter to simplify the generation of an up-to-date RESTful API documentation by combining documentation that’s been hand-written with auto-generated API documentation

•    Java

---

The primary goal of this project is to simplify the generation of an up-to-date RESTful API documentation by combining documentation that’s been hand-written with auto-generated API documentation produced by Swagger. The result is intended to be an up-to-date, easy-to-read, on- and offline user guide, comparable to GitHub’s API documentation. The output of Swagger2Markup can be used as an alternative to swagger-ui and can be served as static content. NOTE: The Swagger Specification has been donated to to the Open API Initiative (OAI) and has been renamed to the OpenAPI Specification. Swagger2Markup converts a Swagger JSON or YAML file into several AsciiDoc or GitHub Flavored Markdown documents which can be combined with hand-written documentation. The Swagger source file can be located locally or remotely via HTTP. Swagger2Markup supports the Swagger 1.2 and 2.0 specification. Internally it uses the official swagger-parser and my markup-document-builder.

api documentation swagger asciidoc markdown

flasgger - Easy Swagger UI for your Flask API

•    Python

---

Flasgger is a Flask extension to extract OpenAPI=Specification from all Flask views registered in your API. Flasgger also comes with SwaggerUI embedded so you can access http://localhost:5000/apidocs and visualize and interact with your API resources.

api flask openapi openapi-specification marshmallow swagger swagger-ui api-documentation api-framework flask-restful restful rest-api

apispec - A pluggable API specification generator

•    Python

---

A pluggable API specification generator. Currently supports the OpenAPI Specification (f.k.a. the Swagger specification). Documentation is available at http://apispec.readthedocs.io/ .

openapi swagger marshmallow rest-api documentation python-3 python-2 flask tornado pluggable api http-api json-schema openapi-specification openapi3 openapi2

datamodel-code-generator - Pydantic model generator for easy conversion of JSON, OpenAPI, JSON Schema, and YAML data sources

•    Python

---

This code generator creates pydantic model from an openapi file and others. See documentation for more details.

yaml csv generator code-generator json-schema swagger openapi swagger-codegen datamodel openapi-codegen pydantic fastapi

go-swagger - Swagger 2.0 implementation for go

•    Go

---

This package contains a golang implementation of Swagger 2.0 (aka OpenAPI 2.0): it knows how to serialize and deserialize swagger specifications. Swagger is a simple yet powerful representation of your RESTful API.

swagger-codegen api code-generator swagger-specification swagger-spec

swagger-ui - Swagger UI is a collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API

•    Javascript

---

👉🏼 Want to score an easy open-source contribution? Check out our Good first issue label. 🕰️ Looking for the older version of Swagger UI? Refer to the 2.x branch.

swagger swagger-ui swagger-api swagger-js rest rest-api openapi-specification oas openapi

safrs - SqlAlchemy Flask-Restful Swagger Json:API OpenAPI

•    Python

---

SAFRS is an acronym for SqlAlchemy Flask-Restful Swagger. The purpose of this framework is to help python developers create a self-documenting JSON API for sqlalchemy database objects and relationships. These objects can be serialized to JSON and can be created, retrieved, updated and deleted through the JSON API. Optionally, custom resource object methods can be exposed and invoked using JSON. Class and method descriptions and examples can be provided in yaml syntax in the code comments. The description is parsed and shown in the swagger web interface. The result is an easy-to-use swagger/OpenAPI and JSON:API compliant API implementation.

flask json sqlalchemy json-api rest-api swagger openapi python3 flask-sqlalchemy flask-restful openapi3

swagger-parser - Swagger Spec to Java POJOs

•    Java

---

This is the swagger parser project, which reads OpenAPI Specifications into current Java POJOs. It also provides a simple framework to add additional converters from different formats into the Swagger objects, making the entire toolchain available. The goal of Swagger™ is to define a standard, language-agnostic interface to REST APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined via Swagger, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interfaces have done for lower-level programming, Swagger removes the guesswork in calling the service.

swagger swagger-parser openapi-specification rest rest-api

AspNetCore.Docs - Documentation for ASP.NET Core

•    CSharp

---

This repository contains the conceptual ASP.NET Core documentation hosted at docs.microsoft.com/aspnet/core. See the Contributing Guide and the issues list if you would like to help. API documentation changes are made in the AspNetApiDocs repository against the triple slash /// comments.

docs aspnetcore aspnet-core

connexion - Swagger/OpenAPI First framework for Python on top of Flask with automatic endpoint validation & OAuth2 support

•    Python

---

Connexion is a framework on top of Flask that automagically handles HTTP requests based on OpenAPI 2.0 Specification (formerly known as Swagger Spec) of your API described in YAML format. Connexion allows you to write a Swagger specification, then maps the endpoints to your Python functions; this makes it unique, as many tools generate the specification based on your Python code. You can describe your REST API in as much detail as you want; then Connexion guarantees that it will work as you specified.With Connexion, you write the spec first. Connexion then calls your Python code, handling the mapping from the specification to the code. This incentivizes you to write the specification so that all of your developers can understand what your API does, even before you write a single line of code.

openapi api-rest swagger flask-extensions

swagger-js - Javascript library to connect to swagger-enabled APIs via browser or nodejs

•    Javascript

---

Swagger Client is a JavaScript module that allows you to fetch, resolve, and interact with Swagger/OpenAPI documents. This is the new version of swagger-js, 3.x. The new version supports Swagger 2.0 as well as OpenAPI 3.

swagger swagger-js swagger-api rest rest-api openapi-specification oai js spec resolver json-refs

awesome-openapi3 - 😎 A list of awesome projects related to OpenAPI 3.0.x, curated by the community

•    

---

A list of awesome projects related to OpenAPI 3.0.x. Pull requests should be against the tools.yaml file in the docs/_data directory.

openapi openapi3 swagger api documentation generation client server converter oas oas3 oasv3

spectral - A flexible JSON/YAML linter for creating automated style guides, with baked in support for OpenAPI v2 & v3

•    TypeScript

---

Find more installation methods in our documentation. Spectral, being a generic YAML/JSON linter, needs a ruleset in order to be able to lint files. You can learn more about the rulesets here.

json linting json-schema swagger openapi oas jsonpath openapi-specification openapi3 json-lint oasv3 json-linter linter json-validator validator schema api

aspnet-api-versioning - Provides a set of libraries which add service API versioning to ASP

•    CSharp

---

ASP.NET API versioning gives you a powerful, but easy-to-use method for adding API versioning semantics to your new and existing REST services built with ASP.NET. The API versioning extensions define simple metadata attributes and conventions that you use to describe which API versions are implemented by your services. You don't need to learn any new routing concepts or change the way you implement your services in ASP.NET today.The default API versioning configuration is compliant with the versioning semantics outlined by the Microsoft REST Guidelines. There are also a number of customization and extension points available to support transitioning services that may not have supported API versioning in the past or supported API versioning with semantics that are different from the Microsoft REST versioning guidelines.

aspnetcore versioning versioning-semantics odata webapi

aspnet-api-versioning - Provides a set of libraries which add service API versioning to ASP

•    CSharp

---

ASP.NET API versioning gives you a powerful, but easy-to-use method for adding API versioning semantics to your new and existing REST services built with ASP.NET. The API versioning extensions define simple metadata attributes and conventions that you use to describe which API versions are implemented by your services. You don't need to learn any new routing concepts or change the way you implement your services in ASP.NET today. The default API versioning configuration is compliant with the versioning semantics outlined by the Microsoft REST Guidelines. There are also a number of customization and extension points available to support transitioning services that may not have supported API versioning in the past or supported API versioning with semantics that are different from the Microsoft REST versioning guidelines.

aspnetcore versioning webapi odata versioning-semantics