shipapis
StarSubmit an APISubmit API

IPGEO vs Parkleitsystem API

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

APIIPGEOHEALTHY76Parkleitsystem APIHEALTHY86
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms2661097
P95 · ms20834508
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGEO vs Parkleitsystem API: common questions

Which is more reliable, IPGEO or Parkleitsystem API?

On our scheduled checks, Parkleitsystem API leads on measured uptime — IPGEO at 99.02% versus Parkleitsystem API at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, IPGEO or Parkleitsystem API?

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

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

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

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