Parkhaus Basel API vs WakaTime

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

Uptime · 30d
Uptime · 90d99.44%100%
Uptime · 30d100%100%
P50 · ms681753
P95 · ms48852993
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree public endpoints; personal data needs API key/OAuth
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Parkhaus Basel API vs WakaTime: common questions

Which is more reliable, Parkhaus Basel API or WakaTime?

On our scheduled checks, WakaTime leads on measured uptime — Parkhaus Basel API at 99.44% versus WakaTime 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, Parkhaus Basel API or WakaTime?

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

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

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

Only Parkhaus Basel API is browser-friendly — it returns CORS headers over HTTPS. WakaTime needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Parkhaus Basel API and WakaTime free for commercial use?

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