Quickstart

World Data API gives you structured access to countries, cities, airports, currencies, timezones, holidays, and more — all interconnected through a single REST interface. No SDK required.

Make your first request#

The API works out of the box with anonymous access, so you can start exploring immediately. Let's fetch information about Japan:

bash
curl "https://worlddataapi.com/v1/countries/JP"
json
{
	"code": "JP",
	"code_alpha3": "JPN",
	"code_numeric": 392,
	"name": "Japan",
	"official_name": "Japan",
	"continent": "Asia",
	"cctld": ".jp",
	"currencies": ["JPY"],
	"primary_currency": "JPY",
	"languages": ["ja"],
	"primary_language": "ja",
	"timezones": ["Asia/Tokyo"],
	"neighbors": []
}

One request, and you have the country's codes, currency, language, timezone, and neighboring countries. Everything uses international standards — ISO codes, IANA timezones — so the data plays nicely with other systems.

Following the connections#

Notice the JPY in the response? This is an example of standards-based identifiers. You can use this exact value, rely on it to be stable, and use it in other endpoints:

bash
curl "https://worlddataapi.com/v1/currencies/JPY"
json
{
	"code": "JPY",
	"code_numeric": 392,
	"name": "Japanese Yen",
	"symbol": "¥",
	"minor_units": 0,
	"countries": ["JP"]
}

And the currency links back to its countries. This is how most of the World Data API works: resources reference each other, so you can traverse the data in whatever direction your application needs.

Going further#

Anonymous access is great for exploring, but comes with lower rate limits. For production use, grab an API key from the dashboard — the free tier is generous and unlocks higher throughput.

From here:

NextAPI Overview