Directory of API specs in OpenAPI(aka Swagger) 2.0 format.
API access to collection: Go!

Our goal is to create a machine-readable Wikipedia for REST APIs with the following principals:

• 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.

Also, we provide services and consultancy around the Swagger spec and REST APIs in general. You can contact us at [email protected].

What does APIs.guru do?

• Filter out private and non-reliable APIs.
• Convert different formats into OpenAPI(fka Swagger) 2.0
• Fix mistakes, ~80% of spec have some
• Add additional data, like: logo, categories, …
• Update specs on daily basis

Update procedure

All specs are automatically updated from their original source. You can see it under x-origin property inside each of swagger.yaml files. I run update script every day and manually check diffs before commit. If you see some API is not updated for more that 48 hours please open an issue.

Existing integrations

• https://any-api.com - Documentation and Test Consoles for Public APIs
• https://sdks.io - Explore Automatically Generated SDKs
• https://cenit.io - Data integration platform
• commandcar - Curl on steroids
• https://datafire.io - allows you to process and transfer data between APIs, databases, and more
• Material Swagger UI Hub - testing and exploring hub for Material Swagger UI demo
• Paw - The most powerful HTTP client for Mac - You can import definitions and directly play with the APIs, see how.

Also used as test suite in following projects:

• swagger-parser - Swagger 2.0 parser and validator for Node and browsers
• SwaggerProvider - F# Type Provider for Swagger
• ReDoc - Swagger-generated API Reference Documentation
• ardoq-swagger-addon - Ardoq Open API (Swagger) Addon
• swagvali - Module to build validators for Swagger(OpenApi) Request parameters and Response objects.

API spec acceptance criteria

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

Integration with 3rd-party services

We discourage you from using Github RAW links or Git directly, repository structure isn't stable and could be changed in future. Instead, we strongly recomend you to use our REST API.

Licenses

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

Spec sources

Some specs are taken from Open Source projects:

• darklynx/swagger-api-collection - OpenAPI(aka Swagger) spec for Instagram API
• Mermade/bbcparse - OpenAPI(aka Swagger) spec for BBC Nitro API
• amardeshbd/medium-api-specification - OpenAPI (aka Swagger 2.0) spec for Medium API