Public API sources — single page, verified, minimal.
A curated API catalog with official documentation links across public data, finance, logistics, communication, maps, and more.
Follow on XLast verified: August 20, 2026
Indexed API records are prepared as decision support with sources, verification dates, integration context, and usable examples—not merely as a list of outbound links.
Documentation, pricing, and terms are checked against sources owned by the provider.
Where supported, working endpoints, example requests, and real response evidence appear together.
Editorial notes, sources, and last-checked dates stay visible so changes can be reviewed again.
Each guide is written against the linked provider documentation and the catalog records, with the sources listed at the end of the article.
RAWG, IGDB, Steam, PokéAPI, Scryfall and more — compared by auth, rate limits, coverage and whether you can ship them commercially.
10 min readAlAdhan, MuslimSalat, İmsakiyem and Diyanet AwqatSalah compared — calculation methods, official data, high-latitude edge cases and Ramadan calendars.
8 min readHow to use TCMB's official Turkish lira exchange rates — the daily XML feed, the EVDS time series service, buying vs selling rates and the weekend problem.
7 min readEvery record goes through the same steps. This section explains where the information on a catalog page comes from, and which parts are verified and which are not.
Each record starts from the provider's own documentation. Whether an API is official or a community-run wrapper is recorded separately, because that distinction changes what you can expect about its longevity and we do not hide it. Documentation, pricing, terms, and privacy pages are stored as separate links so any claim can be traced back to its source.
Authentication method, what the free tier actually covers, and rate limits are read from the documentation. We do not guess here: if a provider does not publish a limit, the field stays marked as not specified. The word "free" on a marketing page and the real quota in the developer docs are frequently not the same thing, and surfacing that gap is much of the catalog's value.
Where an API supports it, a real endpoint is called and the request, the response, and the test date are attached to the record. You can run the same call yourself in the browser through Test Lab. A single successful test is not an uptime guarantee — it only shows that the endpoint responded as expected on that date.
For a record to count as indexable it needs a sufficient summary, use cases, and verification notes in both languages, a working example, and a review by a human. Records that do not meet all of these stay in the catalog but are not indexed by search engines. When a provider changes its terms the record is reviewed again and the last-checked date is updated.
TR APIs
119
The catalog is built for developers who need to answer one question before integrating anything: which source is right for this job, and is it genuinely free? Someone building a side project cares about keyless options they can start with in minutes; someone building a production system cares about rate limits, the authentication model, and the terms of use. The guides on the blog complete that picture by working through specific domains end to end — weather, payments, geocoding, open data.