shipapis
StarSubmit an APISubmit API

airportsapi vs SBB Open Data

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

APIairportsapiNEW—SBB Open DataNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished6000 req/window · 5999 remaining · resets 2026-07-09 00:00:00+00:00
In directory since2026-07-052026-07-05
operationalpartialdownno data

airportsapi vs SBB Open Data: common questions

Which is more reliable, airportsapi or SBB Open Data?

On our scheduled checks, SBB Open Data leads on measured uptime — airportsapi at —% versus SBB Open Data 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 airportsapi and SBB Open Data need an API key?

Neither needs a paid key — airportsapi is callable with no signup, and SBB Open Data is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call airportsapi and SBB Open Data from the browser?

Only airportsapi is browser-friendly — it returns CORS headers over HTTPS. SBB Open Data needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are airportsapi and SBB Open Data free for commercial use?

airportsapi has unclear commercial terms, and SBB Open Data 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.