Skip to content

API collections by use case

5 curated sets, each made only of APIs that passed our verifier. Start from what you want to build, not from a category name.
  1. A weather app is three requests: turn what the user typed into coordinates, ask for the forecast at those coordinates, and decorate the answer. All three can be done without a key and straight from the browser.

    Open-Meteo Geocoding · Open-Meteo Forecast · Open-Meteo Air Quality · Sunrise Sunset · GeoJS · BigDataCloud Reverse Geocoding · +1

  2. The best first API returns a small JSON object, needs no account and works from a plain HTML file. That rules out most "top 10" lists, which are full of APIs that want a key or block browser calls.

    JSONPlaceholder · PokéAPI · Dog CEO · Rick and Morty API · Open Trivia Database · DummyJSON · +3

  3. Brazil has unusually good open data, and most of it is poorly covered by English-language API lists. BrasilAPI alone wraps postal codes, the company registry, holidays, banks and vehicle prices behind one host.

    BrasilAPI — CEP · ViaCEP · BrasilAPI — CNPJ · BrasilAPI — Feriados · Banco Central do Brasil — PTAX · AwesomeAPI — Câmbio · +4

  4. You can build address search, a store locator or a trip planner on open data. The trade-off is that the free public servers are shared, so each has a fair-use policy that you need to respect.

    Photon · Nominatim (OpenStreetMap) · Open-Meteo Geocoding · BigDataCloud Reverse Geocoding · OSRM demo server · Open-Meteo Elevation · +3

  5. A prototype needs data that looks real and a server that answers. These APIs give you both, so you can design the screens before the backend exists.

    JSONPlaceholder · DummyJSON · Random User Generator · httpbin · Postman Echo · Lorem Picsum · +3

Why collections exist

A category tells you what an API is about. It does not tell you which three APIs fit together to finish a project. A weather app needs a geocoder, a forecast and something for the first screen before the user has typed anything; those live in three different categories.

Each collection lists the pieces in the order you would wire them up, says what every piece is for, and ends with the practical steps. Because the entries come from the verified catalog, you can see at a glance whether one of the pieces is having a bad day and swap it.

Questions

How are collections chosen?

Each collection is built around one question, such as "what do I need for a weather app", and lists the APIs from the catalog that fit together, with a line on what each is for.

Are the APIs in a collection checked too?

Yes. A collection only points to catalog entries, and every catalog entry is checked by the verifier. The status next to each API is the same one shown on its own page.

Browse by category

Keep exploring