shipapis
StarSubmit an APISubmit API

OOPSpam vs Parkhaus Basel API

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

APIOOPSpamNEW—Parkhaus Basel APINEW—
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 limit1000 req/window · 999 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OOPSpam vs Parkhaus Basel API: common questions

Which is more reliable, OOPSpam or Parkhaus Basel API?

On our scheduled checks, Parkhaus Basel API leads on measured uptime — OOPSpam at —% versus Parkhaus Basel API 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 OOPSpam and Parkhaus Basel API need an API key?

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

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

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

Are OOPSpam and Parkhaus Basel API free for commercial use?

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