Skip to content
master
Go to file
Code

README.md

banner

APIs in collection OpenAPI definitions Endpoints Chat on Slack

Share on Twitter Follow on Twitter

Directory of API definitions in OpenAPI(fka Swagger) 2.0 and 3.0 formats.
API access to collection: Go! - We also have an RSS Feed

Add API

Our goal is to create the most comprehensive, standards-compliant and up-to-date directory of machine-readable API definitions with the following principles:

  • Open source, community driven project.
  • Only publicly available APIs (free or paid).
  • Anyone can add or change an API, not only API owners.
  • All data can be accessed through a REST API.

If you want to reference this project and you need an icon or even a banner, check our branding guide.

The project was started by Ivan Goncharov of APIs.guru, it is now maintained by Mike Ralphson of Mermade Software. Check out our other OpenAPI-related projects.

APIs.guru provide services and consultancy around the GraphQL and OpenAPI specifications and APIs in general. You can contact us at founders@apis.guru / mike.ralphson@gmail.com

Become a backer

What does APIs.guru do?

  • Filter out private and non-reliable APIs
  • Convert non-OpenAPI formats into OpenAPI 3.0
  • Fix mistakes, ~80% of definitions have some
  • Add additional data, like: logo, categories, …
  • Update definitions on at least a weekly basis

API definition acceptance criteria

  • Public - anyone can access it as long as they follow some clearly defined steps (subscribe, pay fees, etc.).
  • Persistent - API is made with long-lived goal, and not for a particular event (conference, hackathon, etc.).
  • Useful - API should provide useful functionality not only for its owner.

Update procedure

All definitions are automatically updated from their original source. You can see this in the x-origin property within each openapi.yaml or swagger.yaml file. We run our update script at least weekly and automatically revalidate before committing. If you see some APIs are not updated for more than 2 weeks please open an issue.

Own-Label API Directory

Own-Label logo

Do you want an 'own-label' or internal version of the OpenAPI Directory to create your own marketplace or keep track and document both your internal APIs and the external API definitions your organisation depends on? If so contact us now!

Existing integrations

Become a partner

Also used as test suite in the following projects:

  • ReDoc - OpenAPI-generated API Reference Documentation
  • swagger-parser - OpenAPI parser and validator for Node and browsers
  • SwaggerProvider - F# Type Provider for Swagger
  • ardoq-swagger-addon - Ardoq OpenAPI addon
  • swagvali - Module to build validators for OpenAPI Request parameters and Response objects
  • swagger-search - An application that collects and indexes swagger docs from your microservices architecture

Integration with 3rd-party services

We discourage you from using Github RAW links or Git directly, the repository structure may change in the future. Instead, we strongly recommend you to use our REST API.

Licenses

All code is released under the MIT licence.
All API definitions contributed to project by authors are covered by the CC01.0 license.
All API definitions acquired from public sources under the Fair use principle.

Definition sources

Some definitions are taken from Open Source projects:

Contributors

This project exists thanks to all the people who contribute. [Contribute].

Asynchronous APIs

See also AsyncAPI-Directory

Backers

Thank you to all our backers! πŸ™ [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

Partners

Support this project by becoming a partner. Your logo will show up here with a link to your website. [Become a partner]

You can’t perform that action at this time.