StayingAPI vs Transport for Switzerland

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

Uptime · 30d
Uptime · 90d100%92.7%
Uptime · 30d100%100%
P50 · ms143725
P95 · ms9134887
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (powered by Opendata.ch)
Free tierFree — no key required
Rate limitBounded by timetable.search.ch limits (no fixed number published)
In directory since2026-09-212026-07-05
operationalpartialdownno data

StayingAPI vs Transport for Switzerland: common questions

Which is more reliable, StayingAPI or Transport for Switzerland?

On our scheduled checks, StayingAPI leads on measured uptime — StayingAPI at 100% versus Transport for Switzerland at 92.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, StayingAPI or Transport for Switzerland?

StayingAPI has the lower median latency in our checks — StayingAPI responds in 143 ms versus Transport for Switzerland at 725 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 StayingAPI and Transport for Switzerland need an API key?

Transport for Switzerland needs no key, while StayingAPI requires a free API key. If you want to start calling without signup, reach for Transport for Switzerland first.

Can I call StayingAPI and Transport for Switzerland from the browser?

Only Transport for Switzerland is browser-friendly — it returns CORS headers over HTTPS. StayingAPI needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are StayingAPI and Transport for Switzerland free for commercial use?

StayingAPI has unclear commercial terms, and Transport for Switzerland 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.