shipapis
StarSubmit an APISubmit API

LatLng vs Parkleitsystem API

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

APILatLngHEALTHY89Parkleitsystem APIHEALTHY86
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms8551097
P95 · ms21714508
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit60 req/window · 59 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LatLng vs Parkleitsystem API: common questions

Which is more reliable, LatLng or Parkleitsystem API?

Both are neck-and-neck — LatLng 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, LatLng or Parkleitsystem API?

LatLng has the lower median latency in our checks — LatLng responds in 855 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 LatLng and Parkleitsystem API need an API key?

Neither needs a paid key — LatLng 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 LatLng and Parkleitsystem API from the browser?

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

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