shipapis
StarSubmit an APISubmit API

IPGeolocation vs Parkhaus Basel API

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

APIIPGeolocationREACHABLE—Parkhaus Basel APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — 1000 requests/dayFree — limits not published
Rate limit1000 requests/day on free planUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPGeolocation vs Parkhaus Basel API: common questions

Which is more reliable, IPGeolocation or Parkhaus Basel API?

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

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

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

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

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