Openapi Specification

Alternatives To Openapi Specification
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Fastapi68,4551382,959a day ago183October 30, 2023469mitPython
FastAPI framework, high performance, easy to learn, fast to code, ready for production
Openapi Specification27,899
a day ago377apache-2.0JavaScript
The OpenAPI Specification Repository
Swagger Ui25,2171,622424a day ago273November 22, 20231,087apache-2.0JavaScript
Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.
Openapi Generator19,1483643a day ago59November 13, 20234,455apache-2.0Java
OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
Swagger Codegen16,361152254 days ago52November 21, 20233,365apache-2.0Mustache
swagger-codegen contains a template-driven engine to generate documentation, API clients and server stubs in different languages by parsing your OpenAPI / Swagger definition.
Swagger Editor8,570135374 days ago332December 06, 2023240apache-2.0JavaScript
Swagger Editor
Api Platform8,234
3 days ago37February 12, 2018612mitTypeScript
Create REST and GraphQL APIs, scaffold Jamstack webapps, stream changes in real-time.
Swagger Core7,3181,9281,32010 days ago41October 16, 2023771apache-2.0Java
Examples and server integrations for generating the Swagger API Specification, which enables easy access to your REST API
Mockoon5,7058a day ago50December 01, 202365otherTypeScript
Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
Goa5,412772 days ago132November 03, 20238mitGo
🌟 Goa: Elevate Go API development! 🚀 Streamlined design, automatic code generation, and seamless HTTP/gRPC support. ✨
Alternatives To Openapi Specification
Select To Compare


Alternative Project Comparisons
Readme

The OpenAPI Specification

Build Status Issue triagers

The OpenAPI Specification is a community-driven open specification within the OpenAPI Initiative, a Linux Foundation Collaborative Project.

The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface description for HTTP APIs. This allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. When properly defined via OpenAPI, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interface descriptions have done for lower-level programming, the OpenAPI Specification removes guesswork in calling a service.

Use cases for machine-readable API definition documents include, but are not limited to: interactive documentation; code generation for documentation, clients, and servers; and automation of test cases. OpenAPI documents describe API services and are represented in YAML or JSON formats. These documents may be produced and served statically or generated dynamically from an application.

The OpenAPI Specification does not require rewriting existing APIs. It does not require binding any software to a service the described service may not even be owned by the creator of its description. It does, however, require that the service's capabilities be described in the structure of the OpenAPI Specification. Not all services can be described by OpenAPI this specification is not intended to cover every possible style of HTTP APIs, but does include support for REST APIs. The OpenAPI Specification does not mandate a specific development process such as design-first or code-first. It does facilitate either technique by establishing clear interactions with an HTTP API.

This GitHub project is the starting point for OpenAPI. Here you will find the information you need about the OpenAPI Specification, simple examples of what it looks like, and some general information regarding the project.

Current Version - 3.1.0

The current version of the OpenAPI specification is OpenAPI Specification 3.1.0.

Previous Versions

This repository also contains all previous versions.

Each folder in this repository, such as examples and schemas, should contain folders pertaining to the current and previous versions of the specification.

See It in Action

If you just want to see it work, check out the list of current examples.

Tools and Libraries

Looking to see how you can create your own OpenAPI definition, present it, or otherwise use it? Check out the growing list of implementations.

Participation

The current process for developing the OpenAPI Specification is described in Development Guidelines. Developing the next version of the OpenAPI Specification is guided by the Technical Steering Committee (TSC). This group of committers bring their API expertise, incorporate feedback from the community, and expand the group of committers as appropriate. All development activity on the future specification will be performed as features and merged into this branch. Upon release of the future specification, this branch will be merged to main.

The TSC holds weekly web conferences to review open pull requests and discuss open issues related to the evolving OpenAPI Specification. Participation in weekly calls and scheduled working sessions is open to the community. You can view the entire OpenAPI technical meeting calendar online.

The OpenAPI Initiative encourages participation from individuals and companies alike. If you want to participate in the evolution of the OpenAPI Specification, consider taking the following actions:

  • Review the current specification. The human-readable markdown file is the source of truth for the specification.
  • Review the development process so you understand how the spec is evolving.
  • Check the issues and pull requests to see if someone has already documented your idea or feedback on the specification. You can follow an existing conversation by subscribing to the existing issue or PR.
  • Subscribe to an open issue a day (or a week) in your inbox via CodeTriage.com.
  • Create an issue to describe a new concern. If possible, propose a solution.

Not all feedback can be accommodated, and there may be solid arguments for or against a change being appropriate for the specification.

Licensing

See: License (Apache-2.0)

Popular Openapi Projects
Popular Rest Projects
Popular Application Programming Interfaces Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Javascript
Rest
Swagger
Openapi
Web Api
Openapi Specification
Oas