
Posted on ยท 4 min read
7 Public API Directories in 2026: Where to Find Free APIs That Still Work
On this page ยท 9 sections
A directory of APIs is only useful if two things are true. Somebody is still updating it, and it tells you what you need to know before you click: does the API need a key, does it work from a browser, and is it even still online.
We maintain the public-apis list, so we have an interest here and you should weigh our opinions with that in mind. The numbers below are ones you can check yourself. We read them from GitHub's API and each site on November 16, 2026.
Directory | Size | Last updated | Shows auth and CORS | Shows uptime |
|---|---|---|---|---|
public-apis (GitHub) | 2,413 APIs | Nov 15, 2026 | Yes | No |
Public APIs (this site) | 2,413 APIs | Daily | Yes | Yes |
APIs.guru | 2,529 APIs | Apr 20, 2026 | In the spec | No |
public-api-lists | Not counted | Sep 14, 2026 | Yes | No |
n0shake/Public-APIs | Not counted | May 3, 2026 | No | No |
RapidAPI Hub | Marketplace | Live | One key for all | Per API |
Postman API Network | Collections | Live | In the collection | No |
#1. public-apis on GitHub
This is the list most of the others started from. It had 499,534 stars and 55,997 forks when we checked, and the last merged pull request was the day before.
Every entry is one table row: name, description, auth type, HTTPS and CORS. That's its strength. You can scan a whole category in a few seconds and see which APIs need no key. Every change comes through a pull request that a person reviews.
Its limit is that a README can't tell you whether an API is still alive. An entry stays until somebody notices it's dead and opens a pull request to remove it.
#2. Public APIs (This Site)
This site is the same list with the missing part added. Once a day we request every API in it and record the result. On November 16, 2,192 of the 2,413 were up, and 214 had failed three or more checks in a row.
So each API page shows the latest check and a 30-day history, and APIs on a failing streak drop out of the rankings. You can filter by auth, HTTPS and CORS, and there are pages for alternatives and side-by-side comparisons.
#3. APIs.guru
APIs.guru collects machine-readable definitions, not links. Its own metrics endpoint reported 2,529 APIs, 3,992 OpenAPI specs and 108,837 endpoints. If you want to generate a client or feed a spec to a tool, this is the place.
Two caveats. The same endpoint reported 166 APIs as unreachable and 688 specs as invalid. And the repository behind it was last pushed on April 20, 2026. It also leans heavily toward big cloud platforms: 1,829 of the specs are Azure's.
#4. public-api-lists
A separate community list on GitHub with 16,402 stars. It uses the same table format, with auth, HTTPS and CORS columns. Its last push was September 14, 2026, so check anything you find there against a live source.
#5. n0shake/Public-APIs
An older GitHub list with 24,118 stars. It's organised around well-known companies and products, which makes it good for answering "does this service have an API at all". It doesn't have auth or CORS columns, and its last push was May 3, 2026.
#6. RapidAPI Hub
RapidAPI is a marketplace. You sign up once and use one key for every API on it, with billing in one place. Several APIs in our own list are served through it.
That convenience is also the trade-off. You're calling the API through RapidAPI, with RapidAPI's key and limits, and many listings are paid or have a small free quota. It's a good place to buy an API and a poor place to look for something free and direct.
#7. Postman API Network
Postman's public network is a directory of collections you can fork and run. It's most useful once you've already picked an API and want working requests without reading the docs first. It isn't built for browsing by category or for filtering by auth.
#Two Directories That Are Gone
ProgrammableWeb was the original API directory. Its site no longer accepts connections.
any-api.com now redirects to the APILayer marketplace. If you have old bookmarks or tutorials pointing at either, they won't help you.
That's the pattern with directories. The ones that last are either maintained by a community in the open, or kept current by something automated.
#How to Use a Directory Well
Start with a list that shows auth and CORS, so you can rule things out fast. Then confirm the API is alive, either with a directory that checks or with your own curl. Then read the API's own terms for rate limits and commercial use, because no directory tracks those well.
If the project matters, prefer an API with a company behind it. That's why we point people to APILayer for the things a product depends on. And if you know an API that's missing from the list, here's how to submit it.
Happy building.