shipapis
StarSubmit an APISubmit API

ISO 3166-2 API vs Zipcodestack

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

APIISO 3166-2 APIHEALTHY84ZipcodestackDEAD0
Uptime · 30d
Uptime · 90d100%0.0%
Uptime · 30d100%0.0%
P50 · ms1056—
P95 · ms2865—
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ISO 3166-2 API vs Zipcodestack: common questions

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

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

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

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

Yes — both ISO 3166-2 API and Zipcodestack 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 ISO 3166-2 API and Zipcodestack free for commercial use?

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