shipapis
StarSubmit an APISubmit API

ISO 3166 Updates API vs Open-Elevation API

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

APIISO 3166 Updates APINEW—Open-Elevation APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit500 req/windowUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ISO 3166 Updates API vs Open-Elevation API: common questions

Which is more reliable, ISO 3166 Updates API or Open-Elevation API?

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

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

Can I call ISO 3166 Updates API and Open-Elevation API from the browser?

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

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