shipapis
StarSubmit an APISubmit API

BigDataCloud Geocode vs ISO 3166 Updates API

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

APIBigDataCloud GeocodeNEW—ISO 3166 Updates 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 limitUnpublished500 req/window
In directory since2026-07-052026-07-05
operationalpartialdownno data

BigDataCloud Geocode vs ISO 3166 Updates API: common questions

Which is more reliable, BigDataCloud Geocode or ISO 3166 Updates API?

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

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

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

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

BigDataCloud Geocode 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.