shipapis
StarSubmit an APISubmit API

OpenQR vs Parkhaus Basel API

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

APIOpenQRHEALTHY80Parkhaus Basel APIHEALTHY86
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms11251060
P95 · ms28512982
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenQR vs Parkhaus Basel API: common questions

Which is more reliable, OpenQR or Parkhaus Basel API?

Both are neck-and-neck — OpenQR and Parkhaus Basel 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, OpenQR or Parkhaus Basel API?

Parkhaus Basel API has the lower median latency in our checks — OpenQR responds in 1125 ms versus Parkhaus Basel API at 1060 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 OpenQR and Parkhaus Basel API need an API key?

Parkhaus Basel API needs no key, while OpenQR requires a free API key. If you want to start calling without signup, reach for Parkhaus Basel API first.

Can I call OpenQR and Parkhaus Basel API from the browser?

Yes — both OpenQR and Parkhaus Basel API send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are OpenQR and Parkhaus Basel API free for commercial use?

OpenQR has unclear commercial terms, and Parkhaus Basel 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.