Parkhaus Basel API vs restful-api.dev

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

Uptime · 30d
Uptime · 90d100%16.7%
Uptime · 30d100%16.7%
P50 · ms1060240
P95 · ms2982422
Authnonenone
CORSyesyes
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

Parkhaus Basel API vs restful-api.dev: common questions

Which is more reliable, Parkhaus Basel API or restful-api.dev?

On our scheduled checks, Parkhaus Basel API leads on measured uptime — Parkhaus Basel API at 100% versus restful-api.dev at 16.7% 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 restful-api.dev?

restful-api.dev has the lower median latency in our checks — Parkhaus Basel API responds in 1060 ms versus restful-api.dev at 240 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 restful-api.dev need an API key?

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

Can I call Parkhaus Basel API and restful-api.dev from the browser?

Yes — both Parkhaus Basel API and restful-api.dev 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 Parkhaus Basel API and restful-api.dev free for commercial use?

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