shipapis
StarSubmit an APISubmit API

GeoJS vs Parkleitsystem API

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

APIGeoJSHEALTHY100Parkleitsystem APIHEALTHY86
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1071097
P95 · ms7224508
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no API key requiredFree — limits not published
Rate limitUnpublished (no enforced limit stated)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoJS vs Parkleitsystem API: common questions

Which is more reliable, GeoJS or Parkleitsystem API?

Both are neck-and-neck — GeoJS and Parkleitsystem API each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, GeoJS or Parkleitsystem API?

GeoJS has the lower median latency in our checks — GeoJS responds in 107 ms versus Parkleitsystem API at 1097 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do GeoJS and Parkleitsystem API need an API key?

Neither needs a paid key — GeoJS 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 GeoJS and Parkleitsystem API 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 GeoJS and Parkleitsystem API free for commercial use?

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