shipapis
StarSubmit an APISubmit API

ISO 3166 Updates API vs Parkleitsystem API

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

APIISO 3166 Updates APINEW—Parkleitsystem APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
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 Parkleitsystem API: common questions

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

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

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

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

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

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

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