shipapis
StarSubmit an APISubmit API

Transport for Belgium vs Transport for Switzerland

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

APITransport for BelgiumNEW—Transport for SwitzerlandNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (powered by Opendata.ch)
Free tierFree — no keyFree — no key required
Rate limitUnpublishedBounded by timetable.search.ch limits (no fixed number published)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Transport for Belgium vs Transport for Switzerland: common questions

Which is more reliable, Transport for Belgium or Transport for Switzerland?

On our scheduled checks, Transport for Switzerland leads on measured uptime — Transport for Belgium at —% versus Transport for Switzerland 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 Transport for Belgium and Transport for Switzerland need an API key?

Neither needs a paid key — Transport for Belgium is callable with no signup, and Transport for Switzerland is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

Yes — both Transport for Belgium and Transport for Switzerland 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 Transport for Belgium and Transport for Switzerland free for commercial use?

Transport for Belgium 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.