openapi-examples VS openapi-directory

- Directory of SDKs: https://konfigthis.com/sdk/category/all/

For context, we are developer experience enthusiasts and know the pain of searching for an up-to-date SDK for an API, only to find abandoned projects or poorly documented libraries. If you are lucky, some hero developer has published a high-quality SDK, only to eventually fall out-of-date over time, as unpaid work can only last so long.

To generate all the SDKs, we created the highest-quality collection of OpenAPI specifications (https://spec.openapis.org/oas/latest.html) on the internet: https://github.com/konfig-sdks/openapi-examples (it's open and MIT licensed). It contains metadata about the API provider, media assets, response time logs, and the specification itself.

Every specification is modified to ensure that we can create high-quality SDKs. For example, we use LLMs to generate method names for every operation so that the generated SDKs feel natural to use. We then continuously use this dataset to generate SDKs using a generator we have developed over the past 16 months.

I’m excited to know if you have any thoughts or feedback! We also created a Discord server you can join here: https://discord.gg/BAUS4Xtb.

Use APIs.gurufor exploring well-documented OpenAPI files. For example, imagine you are interested in integrating a weather API. By searching for "weather" on APIs.guru, you find several options.

Furthermore, since we can split the generated code into multiple parts based on tag filtering, we can also create different SDKs from different resources or even publicly available APIs. There is an extensive list of publicly available OpenAPI specifications on SwaggerHub, RapidAPI and APIs.guru.

Maybe you'd like to integrate with APIs.guru?

https://apis.guru

In this specific case, I'm auto-publishing (now fully automatically, once a month) a package that wraps content from elsewhere bundling it with some utilities to make that useful in JS and available via NPM. For cases like this it's useful to have a patch update once a month that just updates the upstream content & republishes.

- Crawl API repositories like apis.guru

This should go without saying, but the types inside your API specification should be specific in order to be useful. The main way I see this appear is that some specification generators seem to default to "string" for everything, even if something else makes sense. In an analysis of 1154 specifications from OpenAPI directory, I found that 60% of the field types were strings. Many of these were instances that made sense, such as IDs or names, but many were misused types: for example, there was a year value encoded with type "string," and a boolean value with type "string" and enum "true" or "false". Using too-broad types such as strings can make it harder to understand the specification, and decrease the effectiveness of certain tools.

I haven’t used it but have skimmed through it, but https://apis.guru has collected information on lots of APIs. You might find something interesting.

Try the integration designer with your OpenAPI documents. If you don’t have any document handy, we prepared a few examples for you, or you can find more OpenAPI documents on APIs.guru.

apis.guru is a nice site with APIs listed for many orgs.