shipapis
StarSubmit an APISubmit API

City, Toronto Open Data vs Represent by Open North

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

APICity, Toronto Open DataNEW—Represent by Open NorthNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open; varies by source dataset)
Free tierFree — no key required (CKAN)Free — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Toronto Open Data vs Represent by Open North: common questions

Which is more reliable, City, Toronto Open Data or Represent by Open North?

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

Neither needs a paid key — City, Toronto Open Data is callable with no signup, and Represent by Open North is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call City, Toronto Open Data and Represent by Open North from the browser?

Only Represent by Open North 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 Represent by Open North free for commercial use?

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