shipapis
StarSubmit an APISubmit API

SBB Open Data vs Transport for Los Angeles, US

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

APISBB Open DataNEW—Transport for Los Angeles, USNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit6000 req/window · 5999 remaining · resets 2026-07-09 00:00:00+00:00Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

SBB Open Data vs Transport for Los Angeles, US: common questions

Which is more reliable, SBB Open Data or Transport for Los Angeles, US?

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

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

Can I call SBB Open Data and Transport for Los Angeles, US from the browser?

Only Transport for Los Angeles, US 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 SBB Open Data and Transport for Los Angeles, US free for commercial use?

SBB Open Data has unclear commercial terms, and Transport for Los Angeles, US 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.