shipapis
StarSubmit an APISubmit API

Parkleitsystem API vs Zippopotam.us

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

APIParkleitsystem APINEW—Zippopotam.usNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
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

Parkleitsystem API vs Zippopotam.us: common questions

Which is more reliable, Parkleitsystem API or Zippopotam.us?

On our scheduled checks, Zippopotam.us leads on measured uptime — Parkleitsystem API at —% versus Zippopotam.us 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 Parkleitsystem API and Zippopotam.us need an API key?

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

Can I call Parkleitsystem API and Zippopotam.us from the browser?

Only Zippopotam.us 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 Zippopotam.us free for commercial use?

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