ApiVault VS openapi-directory

It depends on what type of project you're looking for/what type of development you're studying, but if it's web - https://apivault.dev/ is a site someone posted here a while ago that lists and categorizes a bunch of free APIs. I'd find a category you're interested in, and see if there are any APIs that can inspire a project idea around them. Because like the other comment said, if it's not something you're passionate about, it's going to be hard to force yourself to work on it to completion if you're doing this on your own time.

Maybe you can visit this site at all browse api several categories. https://apivault.dev

Apivault

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.