Frequently asked questions
How the catalogue is built and checked, what the badges mean, and what you are allowed to do with any of it.
About this site
What is GetFreeAPIs?
A directory of 2,712 free and public APIs that we check ourselves rather than copying from someone else's list. Every entry records whether it needs a key, whether it supports CORS, whether it runs over HTTPS, and whether it actually responded when we last called it.
Is it really free to use these APIs?
Every API listed has a free tier of some kind, and 1,051 need no key at all. "Free" still varies: some are free for any use, some only for non-commercial use, and some are free up to a request limit. We record what we can verify and link to the provider's own terms for the rest.
How do you check that an API works?
An automated job calls every listing on a schedule, trying HEAD first and falling back to GET, with a timeout and an identifying User-Agent. It records the status code, the response time and whether CORS headers came back. At the last full run, 487 of 2,712 entries were not responding.
What does "no API key required" mean here?
That we sent a request with no key, no token and no Authorization header, and got a successful response. It is a tested claim, not a repeated one. It does not mean unlimited use — most keyless APIs still rate-limit by IP address.
What does CORS mean, and why do you show it?
CORS decides whether browser JavaScript on your site is allowed to read a response from another domain. Without it, a request that works perfectly in curl will fail in a web page. It is the single most common reason a free API turns out to be unusable for a frontend project, which is why we test for it.
An API listed here is down or has changed. What now?
Our status badges come from scheduled checks, so a change usually appears within a day. If something is wrong before we catch it, tell us through the contact page and we will correct the entry.
Can I submit an API to the directory?
Yes. Use the submit page. We check anything submitted the same way we check everything else, so a listing only appears once it has actually responded to us.
Where does the catalogue data come from?
Entries are aggregated from public sources including public-apis, public-api-lists and freepublicapis, then normalised and independently verified by our own checks. The health, latency and CORS data is entirely our own.
Do you make money from this site?
The site carries advertising to cover hosting and the cost of running the checks. Ads never influence which APIs are listed, how they are ranked, or what the status badges say, and our editorial policy sets out where that line sits.
Can I use your data in my own project?
The listings are aggregated from public sources under their own licences. Our measurements — status, latency, reliability and CORS results — are ours, and you are welcome to cite them with a link back. Get in touch if you want something more systematic.
Questions about a specific API
Every one of the 2,712 listings answers its own set, generated from what our checks actually found rather than from a template. These are the questions Open-Meteo Ensemble answers on its page:
Questions answered in our articles
51 articles each answer a handful of questions in depth. Browse by what you are trying to do.
Looking for a specific kind of API?
Each of the 56 category pages answers how many APIs it holds, how many need no key, and which responded fastest at our last check.
Still not answered?
If something here is wrong, out of date, or missing, tell us and we will fix the entry. Corrections are the whole point of checking things ourselves.