Skip to content
Free API Today

Find a free API that works today

185 free public APIs you can use without an account. We call each one and show you which are answering.

  • Free, no sign-up
  • No API key needed
  • 185 of 185 working at the last check

Browse by category

All 185 APIs

Each card is one API. The green badge means it answered our test request with the right data at the last check. “Runs in the browser” means a web page can call it directly, with no server of your own.

185 APIs · no key · HTTPS

Build snapshot, not live. One verifier run on , from the machine that built this site. How we check

  • Open-Meteo ForecastWorking

    Hourly and daily weather forecast for any coordinate, from national weather services.

    api.open-meteo.comRuns in the browser859 msup 1 of 1 dayWeather & environment

  • Open-Meteo Air QualityWorking

    Particulate matter, ozone, pollen and other air-quality values per coordinate.

    air-quality-api.open-meteo.comRuns in the browser807 msup 1 of 1 dayWeather & environment

  • Open-Meteo MarineWorking

    Wave height, direction and period forecast for a point at sea.

    marine-api.open-meteo.comRuns in the browser817 msup 1 of 1 dayWeather & environment

  • Open-Meteo Historical WeatherWorking

    Past weather for a coordinate and date range, back to 1940.

    archive-api.open-meteo.comRuns in the browser827 msup 1 of 1 dayWeather & environment

  • Open-Meteo FloodWorking

    River discharge forecast for the river cell nearest to a coordinate.

    flood-api.open-meteo.comRuns in the browser803 msup 1 of 1 dayWeather & environment

  • Open-Meteo ElevationWorking

    Terrain elevation in metres for one or more coordinates.

    api.open-meteo.comRuns in the browser826 msup 1 of 1 dayGeocoding & places

  • Open-Meteo GeocodingWorking

    Turns a place name into coordinates, country, timezone and population.

    geocoding-api.open-meteo.comRuns in the browser1099 msup 1 of 1 dayGeocoding & places

  • wttr.inWorking

    Current conditions and a three-day forecast for a city name, as JSON or plain text.

    wttr.inRuns in the browser822 msup 1 of 1 dayWeather & environment

  • 7Timer!Working

    Numerical weather forecast in 3-hour steps, including astronomy seeing products.

    www.7timer.infoServer only639 msup 1 of 1 dayWeather & environment

  • US National Weather ServiceWorking

    Forecast office, grid and forecast links for a point in the United States.

    api.weather.govRuns in the browser206 msup 1 of 1 dayWeather & environment

  • MET Norway LocationforecastWorking

    Global point forecast from the Norwegian Meteorological Institute.

    api.met.noRuns in the browser696 msup 1 of 1 dayWeather & environment

  • Sunrise SunsetWorking

    Sunrise, sunset, solar noon and twilight times for a coordinate and date.

    api.sunrise-sunset.orgRuns in the browser349 msup 1 of 1 dayWeather & environment

  • SunriseSunset.ioWorking

    Sunrise, sunset, dawn, dusk and golden hour in the local timezone of the coordinate.

    api.sunrisesunset.ioRuns in the browser191 msup 1 of 1 dayWeather & environment

  • USGS Earthquake CatalogWorking

    Earthquake events as GeoJSON, filterable by time, magnitude and area.

    earthquake.usgs.govRuns in the browser432 msup 1 of 1 dayScience & space

  • Carbon Intensity (Great Britain)Working

    Current and forecast carbon intensity of electricity in Great Britain.

    api.carbonintensity.org.ukRuns in the browser1232 msup 1 of 1 dayWeather & environment

  • Open Topo DataWorking

    Elevation lookups from open datasets such as SRTM and ASTER.

    api.opentopodata.orgServer only524 msup 1 of 1 dayGeocoding & places

  • Nominatim (OpenStreetMap)Working

    Forward and reverse geocoding on OpenStreetMap data.

    nominatim.openstreetmap.orgRuns in the browser202 msup 1 of 1 dayGeocoding & places

  • PhotonWorking

    Search-as-you-type geocoder built on OpenStreetMap data.

    photon.komoot.ioRuns in the browser893 msup 1 of 1 dayGeocoding & places

  • Zippopotam.usWorking

    Place name and coordinates for postal codes in more than 60 countries.

    api.zippopotam.usRuns in the browser177 msup 1 of 1 dayGeocoding & places

  • Postcodes.ioWorking

    UK postcode lookup with coordinates, district and constituency.

    api.postcodes.ioRuns in the browser188 msup 1 of 1 dayGeocoding & places

  • BigDataCloud Reverse GeocodingWorking

    City, region and country for a coordinate, meant for client-side use.

    api.bigdatacloud.netRuns in the browser445 msup 1 of 1 dayGeocoding & places

  • geo.api.gouv.frWorking

    French communes, departments and regions with codes, population and outlines.

    geo.api.gouv.frRuns in the browser794 msup 1 of 1 dayGeocoding & places

  • Base Adresse Nationale (France)Working

    Geocoding of French postal addresses, returned as GeoJSON.

    api-adresse.data.gouv.frRuns in the browser828 msup 1 of 1 dayGeocoding & places

  • CountriesNowWorking

    Countries with cities, states, dial codes, ISO codes and population.

    countriesnow.spaceRuns in the browser400 msup 1 of 1 dayGeocoding & places

Start from what you want to build

Sets of APIs that fit together, in the order you would wire them up.

How an API gets on this list, and stays

The check comes first, the listing second.

See the live status

Lists of public APIs are famous for dead links. They are edited by hand, nobody calls the URLs, and an API that shut down two years ago sits next to one that works. This catalog is built the other way round.

  1. One sample request per API. Every entry carries a real GET request and a rule for a healthy answer, usually a JSON field that must be present. You see the same request on the API’s page.
  2. The verifier calls it. It allows five seconds, requires a 2xx status and applies the rule to the body. It also records the latency and whether the answer carried CORS headers.
  3. Results are kept per day. The scheduled job runs every 30 minutes, 36 APIs at a time, and keeps a 30-day history, so you can tell an API that had one bad hour from one that is gone.
  4. Failing entries are visible. An API that stops answering is shown as down with the reason. It is removed from the catalog only when it does not come back.

Everything listed needs no API key and uses HTTPS. That is a narrower promise than “the biggest list”, and one we can keep. The details, including what the verifier cannot see, are on the status page.

Why use this catalog

Checked by a real request
The verifier sends the sample GET shown on each page and looks for a specific field in the answer. A ping or an HTTP 200 is not enough.
CORS measured, not copied
It sends an Origin header and reads Access-Control-Allow-Origin, so the "runs in the browser" mark reflects what a browser would get.
No proxy in the middle
"Send request" goes from your browser straight to the API. For APIs without CORS we show the stored response instead of relaying your traffic.
History, not a badge
One counter per day for 30 days. A short history is shown as "Up 1 of 1 day checked", never rounded up to a percentage.
Snapshot is called a snapshot
Results from the build machine are dated and labelled. Only data written by the scheduled verifier is presented as such.
The data is yours too
The catalog and the latest results are served as JSON at /api.json with CORS enabled.

Questions

What does "verified" mean here?

Each API has a sample GET request and a rule for what the answer must contain, usually a specific JSON field. Our verifier sends the request with a five-second limit and marks the API as up only when the status is 2xx and the rule holds. An HTTP 200 with an error message inside counts as down.

Do I need an API key for any of these?

No. All 185 entries answered the verifier without a key, token or account. Some have a keyless rate limit and offer a key for higher volumes; where we know the limit, the API page says so.

How do I know if I can call an API from the browser?

Look for the CORS mark. The verifier sends an Origin header and reads Access-Control-Allow-Origin in the answer. In the Oct 3, 2026 run, 169 of 185 APIs allowed browser calls. The others have to be called from a server.

Is the status live?

It depends on what the page says next to the results. "Build snapshot" means one verifier run on the date shown, shipped with the site. "Scheduled verifier" means the results came from the recurring job, with the time of the last run. The label is always there; we never present a snapshot as live.

Why is this list smaller than the big GitHub lists?

Because an entry is only kept if it passes the verifier, needs no key and has a sample request we can show. Lists with thousands of links are not checked and include APIs that are gone, moved or now paid.

Can I use the catalog in my own project?

Yes. The catalog and the latest results are published as JSON at /api.json, with CORS enabled. See the Open data page for the fields.

Keep exploring