CountryStateCity vs ISO 3166-2 API

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms1056
P95 · ms2865
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CountryStateCity vs ISO 3166-2 API: common questions

Which is more reliable, CountryStateCity or ISO 3166-2 API?

On our scheduled checks, ISO 3166-2 API leads on measured uptime — CountryStateCity at 0.0% versus ISO 3166-2 API at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do CountryStateCity and ISO 3166-2 API need an API key?

ISO 3166-2 API needs no key, while CountryStateCity requires a free API key. If you want to start calling without signup, reach for ISO 3166-2 API first.

Can I call CountryStateCity and ISO 3166-2 API from the browser?

Yes — both CountryStateCity and ISO 3166-2 API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are CountryStateCity and ISO 3166-2 API free for commercial use?

CountryStateCity has unclear commercial terms, and ISO 3166-2 API has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.