shipapis
StarSubmit an APISubmit API

ApogeoAPI vs ISO 3166 Updates API

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

APIApogeoAPINEW—ISO 3166 Updates APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished500 req/window
In directory since2026-07-052026-07-05
operationalpartialdownno data

ApogeoAPI vs ISO 3166 Updates API: common questions

Which is more reliable, ApogeoAPI or ISO 3166 Updates API?

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

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

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

Only ISO 3166 Updates API is browser-friendly — it returns CORS headers over HTTPS. ApogeoAPI needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are ApogeoAPI and ISO 3166 Updates API free for commercial use?

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