CountryStateCity vs Parkleitsystem API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CountryStateCity vs Parkleitsystem API: common questions

Which is more reliable, CountryStateCity or Parkleitsystem API?

On our scheduled checks, Parkleitsystem API leads on measured uptime — CountryStateCity 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 CountryStateCity and Parkleitsystem API need an API key?

Parkleitsystem API needs no key, while CountryStateCity requires a free API key. If you want to start calling without signup, reach for Parkleitsystem API first.

Can I call CountryStateCity and Parkleitsystem API from the browser?

Only CountryStateCity 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 CountryStateCity and Parkleitsystem API free for commercial use?

CountryStateCity 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.