APIs.guru OpenAPI Directory
repository·main·Indexed 26 days ago
https://github.com/apis-guru/openapi-directoryA community-driven, open-source directory of machine-readable public API definitions using OpenAPI 2.0 and 3.x formats. The collection is accessible via a REST API and provides validated specifications with origin tracking via the x-origin property.
What's inside APIs.guru
Use official APIs.guru logos and branding
mainWhen attributing the project, use only the official logos provided below.
Logo Assets:
- Logo: https://apis.guru/branding/logo.svg
- Horizontal logo: https://apis.guru/branding/logo_horizontal.svg
- Vertical logo: https://apis.guru/branding/logo_vertical.svg
Naming and Typography:
- The correct spelling is APIs.guru (preserve the exact casing).
- If you are not using the logo with the name included, use the Sansation font.
Attribute APIs.guru in your product or service
mainIf you are using the APIs.guru directory to power a product or service, you are required to include an attribution link.
Pages displaying information from the directory must include one of the following text formats:
- Powered by <LOGO>
- API definitions supplied by <LOGO>
All attribution links must point to
https://APIs.guru.Add an API to the directory
mainAnyone can add or change an API in the directory. To submit a new API definition, follow the process at the official submission page.
https://apis.guru/add-api/Integrate with APIs.guru services
mainWhen building integrations with the APIs.guru collection, do not use GitHub RAW links or Git directly, as the repository structure may change.
Instead, use the official REST API to access the API definitions.
Use the APIs.guru banner for articles or blog posts
mainIf you are writing an article or blog post about APIs.guru, you may use the official banner image.
Banner URL: https://raw.githubusercontent.com/APIs-guru/openapi-directory/main/branding/banner.svg
API definition acceptance criteria
mainTo be included in the directory, an API definition must meet the following criteria:
- Public: Anyone can access it following clearly defined steps (e.g., subscription or fees).
- Persistent: The API must be intended for long-term use, not for temporary events like conferences or hackathons.
- Useful: The API should provide functional value beyond just serving its owner.
Identify API definition sources
mainAll API definitions in the directory include anx-originproperty within theiropenapi.yamlorswagger.yamlfiles. This property indicates the original source from which the definition was automatically updated.