shipapis
StarSubmit an APISubmit API

Hipsum vs Parkhaus Basel API

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

APIHipsumHEALTHY90Parkhaus Basel APIHEALTHY86
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms7231060
P95 · ms17322982
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

Hipsum vs Parkhaus Basel API: common questions

Which is more reliable, Hipsum or Parkhaus Basel API?

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

Hipsum has the lower median latency in our checks — Hipsum responds in 723 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 Hipsum and Parkhaus Basel API need an API key?

Neither needs a paid key — Hipsum 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 Hipsum and Parkhaus Basel API from the browser?

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

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