Skip to content
Free API Today

Verifier status

185 of 185 checked APIs passed their last check. This page shows every result, the failures first, and explains exactly what the verifier does.
APIs in the catalog
185
working at the last check
185
failed the last check
0
can be called from a browser
169

How to read the table: one row per API, the ones that failed first. “Result” is what the API answered to our test request, “Latency” is how long it took, and “Days up” counts the days it passed out of the days we checked.

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

Latest verifier result for every API, failures first
StatusAPIResultLatencyDays upChecked (UTC)
WorkingBinance market dataHTTP 2002190 ms1/1
WorkingMyMemory TranslationHTTP 2001597 ms1/1
WorkingjsDelivr Data APIHTTP 2001487 ms1/1
WorkingCrossref REST APIHTTP 2001465 ms1/1
WorkingCarbon Intensity (Great Britain)HTTP 2001232 ms1/1
WorkingopenFDAHTTP 2001119 ms1/1
WorkingOpen-Meteo GeocodingHTTP 2001099 ms1/1
WorkingNBP Web API (National Bank of Poland)HTTP 200933 ms1/1
Workingcrates.io APIHTTP 200928 ms1/1
WorkingOpen Food FactsHTTP 200905 ms1/1
WorkingPhotonHTTP 200893 ms1/1
WorkingEurope PMCHTTP 200889 ms1/1
WorkingiNaturalistHTTP 200888 ms1/1
WorkingRandomFoxHTTP 200871 ms1/1
WorkingOpen-Meteo ForecastHTTP 200859 ms1/1
WorkingCleveland Museum of ArtHTTP 200836 ms1/1
WorkingMLB Stats APIHTTP 200834 ms1/1
WorkingJikanHTTP 200830 ms1/1
WorkingBase Adresse Nationale (France)HTTP 200828 ms1/1
WorkingOpen-Meteo Historical WeatherHTTP 200827 ms1/1
WorkingOpen-Meteo ElevationHTTP 200826 ms1/1
Workingwttr.inHTTP 200822 ms1/1
WorkingOpen-Meteo MarineHTTP 200817 ms1/1
WorkingQR Server (goQR.me)HTTP 200811 ms1/1
WorkingFruityviceHTTP 200809 ms1/1
WorkingOpen-Meteo Air QualityHTTP 200807 ms1/1
WorkingOpen-Meteo FloodHTTP 200803 ms1/1
Workinggeo.api.gouv.frHTTP 200794 ms1/1
WorkingRDAP.orgHTTP 200777 ms1/1
WorkingUS Treasury Fiscal DataHTTP 200777 ms1/1
Workingyesno.wtfHTTP 200766 ms1/1
WorkingTimeAPI.ioHTTP 200762 ms1/1
WorkingCityBikesHTTP 200758 ms1/1
WorkingNASA Image and Video LibraryHTTP 200743 ms1/1
Workingdata.police.ukHTTP 200729 ms1/1
WorkingChuck Norris JokesHTTP 200717 ms1/1
WorkingLyrics.ovhHTTP 200714 ms1/1
WorkingBlockchain.com tickerHTTP 200710 ms1/1
WorkingMET Norway LocationforecastHTTP 200696 ms1/1
WorkingLichess APIHTTP 200696 ms1/1
WorkingJokeAPIHTTP 200695 ms1/1
WorkingOpenAlexHTTP 200692 ms1/1
WorkingMeowFactsHTTP 200683 ms1/1
WorkingOpen LibraryHTTP 200680 ms1/1
WorkingDummyJSONHTTP 200679 ms1/1
WorkingWayback Machine AvailabilityHTTP 200670 ms1/1
WorkingGBIFHTTP 200658 ms1/1
Workingwger Workout ManagerHTTP 200654 ms1/1
WorkingCoffee (alexflipnote)HTTP 200652 ms1/1
WorkingOSRM demo serverHTTP 200646 ms1/1
WorkingMusicBrainzHTTP 200641 ms1/1
Working7Timer!HTTP 200639 ms1/1
WorkingThe Cat APIHTTP 200639 ms1/1
WorkingOpenHolidays APIHTTP 200637 ms1/1
WorkingRadio BrowserHTTP 200626 ms1/1
WorkingOpen Trivia DatabaseHTTP 200623 ms1/1
WorkingPoetryDBHTTP 200618 ms1/1
WorkingD&D 5e APIHTTP 200614 ms1/1
WorkingTVmazeHTTP 200613 ms1/1
WorkingUseless FactsHTTP 200612 ms1/1
WorkingThe Color APIHTTP 200611 ms1/1
WorkingWhere the ISS at?HTTP 200607 ms1/1
WorkingEmojiHubHTTP 200604 ms1/1
WorkingThe Met CollectionHTTP 200599 ms1/1
WorkingSWAPI (swapi.tech)HTTP 200586 ms1/1
Workingrandom.dogHTTP 200586 ms1/1
WorkinghttpbinHTTP 200584 ms1/1
Workingmath.js web serviceHTTP 200576 ms1/1
WorkingNVD CVE APIHTTP 200574 ms1/1
WorkingicanhazdadjokeHTTP 200567 ms1/1
WorkingAdvice SlipHTTP 200547 ms1/1
WorkingDisney APIHTTP 200526 ms1/1
WorkingOpen Topo DataHTTP 200524 ms1/1
WorkingNHL web APIHTTP 200498 ms1/1
WorkingLaunch Library 2HTTP 200496 ms1/1
WorkingKitsuHTTP 200493 ms1/1
WorkingDog CEOHTTP 200493 ms1/1
WorkingFederal RegisterHTTP 200485 ms1/1
WorkingGenderizeHTTP 200483 ms1/1
WorkingVATComplyHTTP 200482 ms1/1
WorkingAgifyHTTP 200472 ms1/1
WorkingPubChem PUG RESTHTTP 200470 ms1/1
WorkingNationalizeHTTP 200464 ms1/1
WorkingHacker News APIHTTP 200459 ms1/1
WorkingArt Institute of ChicagoHTTP 200447 ms1/1
WorkingBigDataCloud Reverse GeocodingHTTP 200445 ms1/1
WorkingNewtonHTTP 200441 ms1/1
Workingendoflife.dateHTTP 200438 ms1/1
WorkingUSGS Earthquake CatalogHTTP 200432 ms1/1
WorkingBored APIHTTP 200421 ms1/1
Workingbible-api.comHTTP 200416 ms1/1
WorkingWikidataHTTP 200414 ms1/1
WorkingOfficial Joke APIHTTP 200413 ms1/1
WorkingRandom User GeneratorHTTP 200407 ms1/1
WorkingCountriesNowHTTP 200400 ms1/1
Workingmempool.spaceHTTP 200396 ms1/1
WorkingGitLab REST API (public data)HTTP 200387 ms1/1
WorkingLorem PicsumHTTP 200380 ms1/1
WorkingSenado Federal — Dados AbertosHTTP 200378 ms1/1
WorkingClinicalTrials.govHTTP 200366 ms1/1
WorkingStack Exchange APIHTTP 200363 ms1/1
Workingdisease.shHTTP 200357 ms1/1
WorkingZenQuotesHTTP 200354 ms1/1
WorkingViaCEPHTTP 200351 ms1/1
WorkingSunrise SunsetHTTP 200349 ms1/1
WorkingWikipedia REST APIHTTP 200347 ms1/1
WorkingUUID ToolsHTTP 200343 ms1/1
WorkingIBGE — LocalidadesHTTP 200342 ms1/1
WorkingarXiv APIHTTP 200336 ms1/1
WorkingCoinGecko (public)HTTP 200334 ms1/1
WorkingIBGE — NomesHTTP 200333 ms1/1
WorkingFoodishHTTP 200333 ms1/1
WorkingStudio Ghibli APIHTTP 200332 ms1/1
WorkingDeck of CardsHTTP 200322 ms1/1
WorkingCat Facts (catfact.ninja)HTTP 200311 ms1/1
WorkingSpaceflight NewsHTTP 200309 ms1/1
WorkingDeezer APIHTTP 200305 ms1/1
WorkingDiceBearHTTP 200302 ms1/1
WorkingReceitaWSHTTP 200301 ms1/1
WorkingCNPJ.ws (public)HTTP 200296 ms1/1
WorkingBanco Central do Brasil — PTAXHTTP 200293 ms1/1
WorkingipifyHTTP 200283 ms1/1
WorkingPostman EchoHTTP 200282 ms1/1
WorkingCoinbase pricesHTTP 200270 ms1/1
WorkingIBGE — Agregados (SIDRA)HTTP 200261 ms1/1
WorkingThe Trivia APIHTTP 200259 ms1/1
WorkingOpenCEPHTTP 200255 ms1/1
WorkingPackagistHTTP 200252 ms1/1
Workingcdnjs APIHTTP 200248 ms1/1
WorkingDatamuseHTTP 200247 ms1/1
WorkingChess.com Published DataHTTP 200247 ms1/1
WorkingKraken public market dataHTTP 200244 ms1/1
WorkingCâmara dos Deputados — Dados AbertosHTTP 200239 ms1/1
WorkingGoogle Public DNS over HTTPSHTTP 200222 ms1/1
WorkingJSONPlaceholderHTTP 200219 ms1/1
WorkingUS National Weather ServiceHTTP 200206 ms1/1
WorkingNominatim (OpenStreetMap)HTTP 200202 ms1/1
WorkingTransport for London Unified APIHTTP 200201 ms1/1
WorkingBrasilAPI — CNPJHTTP 200198 ms1/1
WorkingHTTP Status DogsHTTP 200197 ms1/1
WorkingSunriseSunset.ioHTTP 200191 ms1/1
WorkingPostcodes.ioHTTP 200188 ms1/1
WorkingBrasilAPI — FIPEHTTP 200187 ms1/1
WorkingFIPE API (Parallelum)HTTP 200187 ms1/1
WorkingBrasilAPI — CEPHTTP 200185 ms1/1
WorkingScryfallHTTP 200184 ms1/1
WorkingFreeToGameHTTP 200181 ms1/1
WorkingRoboHashHTTP 200181 ms1/1
WorkingOpen Brewery DBHTTP 200180 ms1/1
WorkingFrankfurterHTTP 200179 ms1/1
WorkingJolpica F1 (Ergast successor)HTTP 200179 ms1/1
WorkingNager.DateHTTP 200178 ms1/1
WorkingGeoJSHTTP 200178 ms1/1
WorkingMinecraft Server StatusHTTP 200178 ms1/1
WorkingZippopotam.usHTTP 200177 ms1/1
WorkingRick and Morty APIHTTP 200177 ms1/1
Workingipwho.isHTTP 200176 ms1/1
WorkingBrasilAPI — FeriadosHTTP 200176 ms1/1
WorkingYGOPRODeckHTTP 200175 ms1/1
WorkingFlagpedia flag CDNHTTP 200174 ms1/1
WorkingCoinpaprikaHTTP 200173 ms1/1
WorkingAwesomeAPI — CâmbioHTTP 200173 ms1/1
WorkingHTTP CatsHTTP 200173 ms1/1
Workingplacehold.coHTTP 200173 ms1/1
WorkingExchangeRate-API (open access)HTTP 200172 ms1/1
WorkingGutendexHTTP 200172 ms1/1
WorkingCoinLoreHTTP 200171 ms1/1
Workingcountry.isHTTP 200170 ms1/1
WorkingOpen5eHTTP 200170 ms1/1
WorkingWikimedia PageviewsHTTP 200167 ms1/1
WorkingPokéAPIHTTP 200164 ms1/1
WorkingWorld Bank IndicatorsHTTP 200115 ms1/1
WorkingCheapSharkHTTP 20087 ms1/1
WorkingBrasilAPI — BancosHTTP 20082 ms1/1
WorkingBrasilAPI — TaxasHTTP 20079 ms1/1
WorkingiTunes Search APIHTTP 20077 ms1/1
WorkingPwned PasswordsHTTP 20075 ms1/1
WorkingCurrency API (fawazahmed0)HTTP 20075 ms1/1
Workingnpm registryHTTP 20069 ms1/1
WorkingCloudflare DNS over HTTPSHTTP 20068 ms1/1
WorkingPyPI JSON APIHTTP 20066 ms1/1
WorkingBrasilAPI — DDDHTTP 20064 ms1/1
WorkingDEV Community APIHTTP 20048 ms1/1
WorkingNobel Prize APIHTTP 20046 ms1/1
WorkingxkcdHTTP 20043 ms1/1

What the verifier does

The verifier is a small program that runs on a schedule. The same code produces the build snapshot and the scheduled results, so the two are comparable.

  • Request. One GET to the sample URL shown on the API’s page, with the headers that API needs, Origin: https://freeapi.today and User-Agent: FreeApiTodayBot/1.0 (+https://freeapi.today/status).
  • Budget. 5 seconds. No answer in that time is a failure. Redirects are followed.
  • Verdict. The status must be 2xx and the body must satisfy that API’s rule: a named JSON field present, a non-empty array, an image content type, or a known string in a text answer. The rule is printed on each API page under “Availability”.
  • CORS. Recorded as allowed when Access-Control-Allow-Origin is * or our origin.
  • Schedule. Every 30 minutes, 36 APIs per run, in catalog order.
  • History. One counter per API per UTC day, for 30 days. A day is “up” when at least half of its checks passed.

What it cannot tell you

A check is one request, from one place, for one endpoint. It does not test write operations, other endpoints of the same API, or your rate limit. An API can be marked down because it blocks cloud IP ranges and still work from your laptop. Use the “Send request” button on an API’s page to test from your own browser.

What it never does

It never requests a URL that is not written in the catalog, so it cannot be pointed at a target by a visitor. This site has no endpoint that fetches a URL on your behalf.

Questions

How often is each API checked?

The scheduled verifier runs every 30 minutes and checks up to 36 APIs per run, moving through the catalog in order. With 185 entries, each API is checked about once every 180 minutes.

What counts as "down"?

No answer within five seconds, a status outside 200–299, an empty body, a body that is not the promised format, or JSON that lacks the expected field. The reason is shown next to the result.

What does "Up 28 of 30 days" mean?

For each UTC day we count checks and passes. A day counts as up when at least half of its checks passed. The figure is the number of up days over the days we actually have data for, at most 30. A short history is shown as short, for example "Up 1 of 1 day checked".

Where does the verifier run?

On Cloudflare Workers. An API that blocks cloud IP ranges or is only reachable from some countries can look down to the verifier while working for you, and the opposite. Use "Send request" on the API page to test from your own browser.

Does the verifier put load on the APIs?

It sends one small GET per check, identifies itself as FreeApiTodayBot with a link to this page, and waits at most five seconds. It never requests a URL that is not written in the catalog.

Keep exploring