shipapis
StarSubmit an APISubmit API

Transport for Los Angeles, US vs Transport for Toronto, Canada

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

APITransport for Los Angeles, USNEW—Transport for Toronto, CanadaNEW—
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 limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Transport for Los Angeles, US vs Transport for Toronto, Canada: common questions

Which is more reliable, Transport for Los Angeles, US or Transport for Toronto, Canada?

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

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

Can I call Transport for Los Angeles, US and Transport for Toronto, Canada from the browser?

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

Are Transport for Los Angeles, US and Transport for Toronto, Canada free for commercial use?

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