Parkleitsystem API vs GeoJS

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree, no API key required
Rate limitUnpublishedUnpublished (no enforced limit stated)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Parkleitsystem API vs GeoJS: common questions

Which is more reliable, Parkleitsystem API or GeoJS?

Only GeoJS is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Parkleitsystem API and GeoJS need an API key?

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

Can I call Parkleitsystem API and GeoJS from the browser?

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

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