Here you'll find some information about World Data API - if you're here for the legalese, feel free to jump straight to any of these pages:

• Privacy Policy

• Terms of Service

• Contact Us

Working with international data is unreasonably hard.

Not hard in an interesting way. Hard in a tedious, time-consuming way that makes you question your career choices. You need countries, cities, timezones, currencies, airports — and each one lives in a different API with different authentication, different response formats, and different assumptions about how the world works.

The real problem isn't even managing multiple API keys or endpoints. It's making the data interoperate. Which timezone applies to this airport? What currency does this country use — and did that change last year? How do you handle a city that spans two administrative regions? These questions require domain knowledge that's surprisingly difficult to encode correctly. Even modern AI tools struggle with the edge cases without hardcoded special (and usually incorrect!) handling.

Every project that touches international data ends up building some fragile glue code, learning the same painful lessons, and debugging the same subtle inconsistencies.

World Data API is a single interface to countries, cities, airports, timezones, holidays, currencies, languages, and climate data — thoughtfully designed such that every piece of data references other pieces of data correctly.

Query an airport, get its timezone. Query a country, get its neighbors, currencies, and upcoming holidays. The relationships are built in. No need to maintain a mapping table or write translation layers or hope that two different APIs use the same identifier for São Paulo.

Let us handle the standards, interop, and cross-referencing — so that you can stop writing glue code, and start building features instead.

Stability over novelty. The API contract doesn't change underneath you. If we ever release breaking changes, you get proper notice and a migration path.

Data is live, interfaces are stable. Underlying data updates as the world changes — that's the point. But endpoint paths, parameter names, and response schemas stay predictable.

Documentation is part of the product. Every endpoint documented, every field explained, every error contextualized. If the docs are bad, the API is bad.

Pricing is public. No "contact sales" for standard use cases. No feature gating designed to force upgrades. The price is the price.

We're actively expanding coverage — more cities, better airport metadata, additional calendar systems. If there's something missing that would make this useful for your project, we want to hear about it.

World Data API is built and run by an independent developer.

This all started as a side project to scratch a personal itch. It's now a real product because other developers kept having the same itch. There's no VC funding, no growth team, no enterprise sales organization — just a genuine attempt to make international data less painful to work with.

Please send all your feature requests, bug reports, or just feedback in general, using the form in the dashboard. Seriously — I read everything.