shipapis
StarSubmit an APISubmit API

ISO 3166 Updates API vs US ZipCode

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

APIISO 3166 Updates APINEW—US ZipCodeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit500 req/windowUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ISO 3166 Updates API vs US ZipCode: common questions

Which is more reliable, ISO 3166 Updates API or US ZipCode?

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

ISO 3166 Updates API needs no key, while US ZipCode requires a free API key. If you want to start calling without signup, reach for ISO 3166 Updates API first.

Can I call ISO 3166 Updates API and US ZipCode from the browser?

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

ISO 3166 Updates API has unclear commercial terms, and US ZipCode 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.