shipapis
StarSubmit an APISubmit API

City, Toronto Open Data vs OpenRegistry

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

APICity, Toronto Open DataNEW—OpenRegistryNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key required (CKAN)Free tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Toronto Open Data vs OpenRegistry: common questions

Which is more reliable, City, Toronto Open Data or OpenRegistry?

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

City, Toronto Open Data needs no key, while OpenRegistry requires a free API key. If you want to start calling without signup, reach for City, Toronto Open Data first.

Can I call City, Toronto Open Data and OpenRegistry from the browser?

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

Are City, Toronto Open Data and OpenRegistry free for commercial use?

City, Toronto Open Data has unclear commercial terms, and OpenRegistry 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.