shipapis
StarSubmit an APISubmit API

ISO 3166-2 API vs PostalCodes

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

APIISO 3166-2 APINEW—PostalCodesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ISO 3166-2 API vs PostalCodes: common questions

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

On our scheduled checks, PostalCodes leads on measured uptime — ISO 3166-2 API at —% versus PostalCodes at —% 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 ISO 3166-2 API and PostalCodes need an API key?

Neither needs a paid key — ISO 3166-2 API is callable with no signup, and PostalCodes is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

Neither sends browser-friendly CORS headers reliably, so call ISO 3166-2 API and PostalCodes from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

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

ISO 3166-2 API has unclear commercial terms, and PostalCodes 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.