1001 Smart Cities
🇨🇦 Toronto

311 Toronto: Service Requests, Open Data and Service Standards

🤖 AI-generated summary · ◆ 12 sourced claims · 🔎 Last verified

This overview was generated with AI from the public sources listed below and checked against them before publication. It has not had a complete human fact-check — treat it as a starting point and follow the sources.

12 sourced claims on this page, none individually verified yet — turn on “Sources in the text” to see each one.

How this atlas is made · What “last verified” means · What “source-checked” means · The full record behind this page

Every request since 2010 is published as open data, but without a closure date — and in 2011 the Auditor General found that 'closed' did not necessarily mean the service had been provided.

Outcome🔄 Ongoing
Evidence🏛️ Officialgrades the sourcing — this entry states no impact figure
what does this mean?The strongest source is the operator's or the city's own reporting — an official report, dataset or press release. It grades who did the looking — not how well the project went. All four grades →
Run byCity of Toronto — Customer Experience Division (311 Toronto)
Scale🏙️ City-wide

Part of 1001 Smart Cities — 1,247 documented projects · 🏙️ 9 more in Toronto · 🪪 Digital government guide · 🏛️ Governance projects

Toronto's 311 line opened on 24 September 2009 and takes non-emergency requests around the clock, with interpretation offered in more than 180 languages. Service requests are published as open data — one archive per calendar year since 2010, refreshed monthly — but the extract carries creation date, type, status, division and ward, with no closure date and no service-level target. Those targets sit instead on a separate public dashboard that reports how many requests were addressed within standard, division by division. The city's own glossary concedes a standard 'may be met through an initial investigation rather than full resolution of the issue'.

Live 📅 since 2009

🎓 Lesson

Toronto's Auditor General found in 2011 that a 311 request marked 'closed' did not necessarily mean the service had been provided — it could also mean an investigation had begun, or that the service could not be provided. The city added status categories, but no audit cited here has since tested whether a request marked closed was actually fixed. The closest anyone has come is a February 2025 Auditor General review of the Parks Branch, which found the division had no centralized system to track, log and manage public complaints at all — and the city's own dashboard glossary warns that meeting a standard can mean an initial investigation rather than a repair.

🏛️ GovernanceDigital governmentOpen dataCitizen participation

Sources

↗ City of Toronto — About 311 (FAQ)Operator page, hours and languages: 'Customer service representatives are available to answer your questions or fill a service request 24 hours a day, seven days a week', with interpreters available in 'more than 180 languages'.
↗ MobileSyrup — City of Toronto launches 311 service for non-emergency infoPublished 24 September 2009Contemporaneous coverage published 24 September 2009, the launch day, quoting the city: 'This is a pivotal day for customer service for the City of Toronto.' Confirms 24/7 operation and 180 languages at launch. Used for the start year only; no superlative about being first in Canada is claimed.
↗ City of Toronto Open Data — 311 Service Requests, Customer Initiated (CKAN package metadata)Authoritative field and cadence source, queried 2026-07-26: refresh rate monthly, last refreshed 2026-07-08, one ZIP resource per year from 2010 to 2026. Attributes are creation date/time, location, original request type, status (Initiated, In Progress, Canceled, Closed), division, section-unit and ward — there is no closure date, no due date and no service-level target, and no channel column despite the description noting requests arrive by phone, fax, email, web, mobile API and Twitter. Note for the editor: the human-facing page at open.toronto.ca is a JavaScript shell that renders an empty 'Retired' template to fetchers; the dataset is live.
↗ City of Toronto — 311 Service Standard Dashboard: Glossary & NotesThe load-bearing caveat, verbatim: 'A service standard defines the expected timeframe within which a service request is to be addressed or actioned by the responsible City division' and 'In some cases, a service standard may be met through an initial investigation rather than full resolution of the issue.' Requests addressed/actioned are counted 'in accordance with the applicable service standard within a specified timeframe', excluding cancelled requests and those with no standard.
↗ City of Toronto — 311 Service Standard DashboardThe dashboard the targets live on: 'an interactive view of service request volumes, service levels, geographic distribution, and 311 call responsiveness across the city', covering six divisions, with static dashboards for property standards, noise, graffiti, dead wildlife pickup, garbage collection, overflowing bins, potholes, and trees and pruning.
Show 5 more sourcesShow fewer
↗ Auditor General of Toronto — Audit of Parks Branch Operations Phase 2 (5 February 2025)The nearest thing in this series to an independent check on what happens after a 311 complaint is filed, verbatim: 'The Parks Branch does not have a centralized system to effectively track, log and manage public complaints, making it difficult to compile and analyze data to identify trends or address the underlying causes of recurring issues.' The report also says the branch can improve its targets for 'assessing, acknowledging, and resolving complaints received from Torontonians'. It audits one division's handling of complaints, not the accuracy of 311 closure codes.
↗ Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized (23 November 2011)Cited for existence and date only: Toronto is one of the few cities in this series whose auditor has examined 311 itself. The report PDF could not be parsed in this environment, so no figure from it is used in the entry — including the often-repeated claim about unanswered calls.
↗ City of Toronto — Customer Experience Division Annual Report 2024Published 13 February 2025Origin of every volume figure in the impact field, operator self-reported: 'In 2024, CXD-311 responded to 1.29 million interactions with a Service Level of 82% for the phone', of which about 487,000 became service requests, against a target of answering 80% of calls within 75 seconds. These come from the operator's own report to committee, not from the open dataset.
↗ Open311 GeoReport v2 server directory — Toronto entryRegistration record: jurisdiction_id 'toronto.ca', base_url 'https://secure.toronto.ca/webwizard/ws/', test_url 'https://secure.toronto.ca/open311test/ws/', version 'georeport-v2', production_ready true. Tested 2026-07-26: the production services list returned HTTP 404 and the test server returned HTTP 404. The discovery document at secure.toronto.ca/open311test/discovery.json still resolves but is dated December 2011.
↗ Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized, full report (17 October 2011)The full audit report (Appendix 1). Section B.2 records that during the audit in March 2011 the online status of a request showed only 'open' or 'closed', and that 'closed' did not necessarily mean the service had been provided: it could also mean an investigation had been initiated with service pending, or that service could not be provided for operational reasons. Staff added further status categories in June 2011; Recommendation 3 asks for 'accurate and clear status information on-line'.

📅 How old is the evidence?

Two clocks, kept apart: when this entry’s sources were published, and what has happened to its record in the atlas. Documented span: since 2009. 5 of 10 sources carry a publication date, from 24 September 2009 to 13 February 2025.

When the sources were published

  1. MobileSyrup · pressMobileSyrup — City of Toronto launches 311 service for non-emergency info
  2. Auditor General of Toronto · oversight bodyAuditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized, full report (17 October 2011)
  3. Auditor General of Toronto · oversight bodyAuditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized (23 November 2011)
  4. Auditor General of Toronto · oversight bodyAuditor General of Toronto — Audit of Parks Branch Operations Phase 2 (5 February 2025)
  5. City of Toronto · city governmentCity of Toronto — Customer Experience Division Annual Report 2024

Every source, with links ↑

What happened to this record

  1. Sources last read
  2. Entered the record

Every revision, permanent →

Show your work What this page rests on and what it can’t tell you · all 12 claims with their sources · the forensic record

Evidence file · public beta 12 addressable claims, 10 source dossiers, one permanent baseline. The file is unreviewed — an AI-assisted structural migration, not a human or expert endorsement. Every revision keeps a permanent copy under revision history.

Inspect the claims, one by one — verbatim text, sources and caveats for all 12

The text below is copied verbatim from the published record. Each claim names the source dossiers that carry it; caveats stay attached to the claim they qualify.

Claim 1 clm-213fae0dc4e16135 quantitative
Toronto's 311 line opened on 24 September 2009
Published field
snippet · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
Published on launch day, the article reports the city opening 311 and quotes the mayor calling it a pivotal day for customer service.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. MobileSyrup — City of Toronto launches 311 service for non-emergency info
Claim 2 clm-e3a4b3206d676b3a quantitative
takes non-emergency requests around the clock, with interpretation offered in more than 180 languages
Published field
snippet · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The city's 311 FAQ states that representatives take requests 24 hours a day, seven days a week, with interpreters in more than 180 languages.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. City of Toronto — About 311 (FAQ)
Claim 3 clm-bbb35684d549f8cb quantitative
one archive per calendar year since 2010, refreshed monthly
Published field
snippet · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The dataset's catalogue record lists one resource per year from 2010 onward and a monthly refresh rate.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. City of Toronto Open Data — 311 Service Requests, Customer Initiated (CKAN package metadata)
Claim 4 clm-cfd3a1e3547fad1c descriptive
the extract carries creation date, type, status, division and ward, with no closure date and no service-level target
Published field
snippet · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The catalogue record lists the published attributes — creation date and time, location, original request type, status, division, section-unit and ward — and none of them is a closure date or a target.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. City of Toronto Open Data — 311 Service Requests, Customer Initiated (CKAN package metadata)
Claim 5 clm-daf4e8289f5f92f2 descriptive
Those targets sit instead on a separate public dashboard that reports how many requests were addressed within standard, division by division
Published field
snippet · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The dashboard glossary defines the service level as the share of requests addressed or actioned by the responsible division within the service standard; the dashboard page describes the public view.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. City of Toronto — 311 Service Standard Dashboard: Glossary & Notes
  2. City of Toronto — 311 Service Standard Dashboard
Claim 6 clm-c0b03b644a1562e6 descriptive
a standard 'may be met through an initial investigation rather than full resolution of the issue'
Published field
snippet · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
Quoted verbatim from the city's dashboard glossary.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. City of Toronto — 311 Service Standard Dashboard: Glossary & Notes
Claim 7 clm-f10126f7aa81a334 quantitative
Toronto's Auditor General found in 2011 that a 311 request marked 'closed' did not necessarily mean the service had been provided
Published field
lesson · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
Section B.2 of the audit report states that 'closed' did not necessarily mean the service had been provided.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized, full report (17 October 2011)
Claim 8 clm-4e59a870f02d7613 descriptive
it could also mean an investigation had begun, or that the service could not be provided
Published field
lesson · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The report lists the range of actions 'closed' could mean, including an initiated investigation with service pending and service that could not be provided for operational reasons.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized, full report (17 October 2011)
Claim 9 clm-29d075990d9605b6 descriptive
The city added status categories
Published field
lesson · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The report notes that staff added extra status categories in June 2011 in response to the audit concern.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized, full report (17 October 2011)
Claim 10 clm-88d1b89070f701eb descriptive
no audit cited here has since tested whether a request marked closed was actually fixed
Published field
lesson · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The 2011 report describes how the status was displayed and asks for accurate status information; the 2025 review examined one branch's complaint handling. Neither reports sampling closed requests against the work done.
Caveat
This describes the stated scope of the two reviews; it is not a finding that closures are wrong.

Sources carrying this claim

  1. Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized, full report (17 October 2011)
  2. Auditor General of Toronto — Audit of Parks Branch Operations Phase 2 (5 February 2025)
Claim 11 clm-5f1b70bddd42e3f1 quantitative
a February 2025 Auditor General review of the Parks Branch, which found the division had no centralized system to track, log and manage public complaints at all
Published field
lesson · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The audit's key findings say the Parks Branch has no centralized system to track, log and manage public complaints.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. Auditor General of Toronto — Audit of Parks Branch Operations Phase 2 (5 February 2025)
Claim 12 clm-021e5e8a77660bd6 descriptive
the city's own dashboard glossary warns that meeting a standard can mean an initial investigation rather than a repair
Published field
lesson · verbatim
Mapping
mapped · no interpretation or interpolation added by this file
What the mapping says
The glossary says a service standard may be met through an initial investigation rather than full resolution of the issue.
Caveat
No claim-specific caveat recorded

Sources carrying this claim

  1. City of Toronto — 311 Service Standard Dashboard: Glossary & Notes
Forensic record — source dossiers, gaps, hashes and the exact revision this page renders

This layer records what is known about each source, what is still missing, and the exact snapshot this page is rendering. A missing date, archive or hash stays visible as missing.

unreviewed Revision 2026-11-04-evidence-baseline effective 2026-11-03 · created 2026-11-04

Awaiting operator and domain-expert review; publication of this revision implies neither.

sha256:47d921204c2d3a3f31121155d5600448fe2a4f3c4c0609291acf435ad8f06803
Revision history → Permanent version link → Machine-readable record → Evidence Constitution →
12
of 12 claims mapped
10
source dossiers
5
publication dates recorded
0
archives linked
0
exact locators
0
content captures hashed

Governance facts carried by the record

Operator
City of Toronto — Customer Experience Division (311 Toronto)
Actor types
city-government
Funding model
public
Funding description
Not recorded
Cost
Not recorded
Ownership
Not recorded
Decision rights
Not recorded
Exit conditions
Not recorded

10 source dossiers

City of Toronto — About 311 (FAQ) toronto.ca · 1 linked claim

Open original source ↗

Stable source ID
src-f16f2586d789107b
Publisher
Name not classified · toronto.ca
Type / language
web-page · language not classified
Published
Not recorded
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

Operator page, hours and languages: 'Customer service representatives are available to answer your questions or fill a service request 24 hours a day, seven days a week', with interpreters available in 'more than 180 languages'.

Descriptive only — not page/paragraph exact
Claims linked
MobileSyrup — City of Toronto launches 311 service for non-emergency info mobilesyrup.com · 1 linked claim

Open original source ↗

Stable source ID
src-9180b0c801fe4a82
Publisher
Name not classified · mobilesyrup.com
Type / language
web-page · language not classified
Published
2009-09-24
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

Contemporaneous coverage published 24 September 2009, the launch day, quoting the city: 'This is a pivotal day for customer service for the City of Toronto.' Confirms 24/7 operation and 180 languages at launch. Used for the start year only; no superlative about being first in Canada is claimed.

Descriptive only — not page/paragraph exact
Claims linked
City of Toronto Open Data — 311 Service Requests, Customer Initiated (CKAN package metadata) ckan0.cf.opendata.inter.prod-toronto.ca · 2 linked claims

Open original source ↗

Stable source ID
src-38f180da60c808e5
Publisher
Name not classified · ckan0.cf.opendata.inter.prod-toronto.ca
Type / language
web-page · language not classified
Published
Not recorded
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

Authoritative field and cadence source, queried 2026-07-26: refresh rate monthly, last refreshed 2026-07-08, one ZIP resource per year from 2010 to 2026. Attributes are creation date/time, location, original request type, status (Initiated, In Progress, Canceled, Closed), division, section-unit and ward — there is no closure date, no due date and no service-level target, and no channel column despite the description noting requests arrive by phone, fax, email, web, mobile API and Twitter. Note for the editor: the human-facing page at open.toronto.ca is a JavaScript shell that renders an empty 'Retired' template to fetchers; the dataset is live.

Descriptive only — not page/paragraph exact
Claims linked
City of Toronto — 311 Service Standard Dashboard: Glossary & Notes toronto.ca · 3 linked claims

Open original source ↗

Stable source ID
src-1eb4001505e3d2ed
Publisher
Name not classified · toronto.ca
Type / language
web-page · language not classified
Published
Not recorded
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

The load-bearing caveat, verbatim: 'A service standard defines the expected timeframe within which a service request is to be addressed or actioned by the responsible City division' and 'In some cases, a service standard may be met through an initial investigation rather than full resolution of the issue.' Requests addressed/actioned are counted 'in accordance with the applicable service standard within a specified timeframe', excluding cancelled requests and those with no standard.

Descriptive only — not page/paragraph exact
Claims linked
City of Toronto — 311 Service Standard Dashboard toronto.ca · 1 linked claim

Open original source ↗

Stable source ID
src-aba9cf1113cea8af
Publisher
Name not classified · toronto.ca
Type / language
web-page · language not classified
Published
Not recorded
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

The dashboard the targets live on: 'an interactive view of service request volumes, service levels, geographic distribution, and 311 call responsiveness across the city', covering six divisions, with static dashboards for property standards, noise, graffiti, dead wildlife pickup, garbage collection, overflowing bins, potholes, and trees and pruning.

Descriptive only — not page/paragraph exact
Claims linked
Auditor General of Toronto — Audit of Parks Branch Operations Phase 2 (5 February 2025) torontoauditor.ca · 2 linked claims

Open original source ↗

Stable source ID
src-e0e74908ad7b7f96
Publisher
Name not classified · torontoauditor.ca
Type / language
web-page · language not classified
Published
2025-02-05
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

The nearest thing in this series to an independent check on what happens after a 311 complaint is filed, verbatim: 'The Parks Branch does not have a centralized system to effectively track, log and manage public complaints, making it difficult to compile and analyze data to identify trends or address the underlying causes of recurring issues.' The report also says the branch can improve its targets for 'assessing, acknowledging, and resolving complaints received from Torontonians'. It audits one division's handling of complaints, not the accuracy of 311 closure codes.

Descriptive only — not page/paragraph exact
Claims linked
Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized (23 November 2011) torontoauditor.ca · background

Open original source ↗

Stable source ID
src-b8c548b33635307a
Publisher
Name not classified · torontoauditor.ca
Type / language
web-page · language not classified
Published
2011-11-23
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

Cited for existence and date only: Toronto is one of the few cities in this series whose auditor has examined 311 itself. The report PDF could not be parsed in this environment, so no figure from it is used in the entry — including the often-repeated claim about unanswered calls.

Descriptive only — not page/paragraph exact
Claims linked
Background source; no baseline claim points here
City of Toronto — Customer Experience Division Annual Report 2024 toronto.ca · background

Open original source ↗

Stable source ID
src-9a9fa0386c56cf1d
Publisher
Name not classified · toronto.ca
Type / language
pdf · language not classified
Published
2025-02-13
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

Origin of every volume figure in the impact field, operator self-reported: 'In 2024, CXD-311 responded to 1.29 million interactions with a Service Level of 82% for the phone', of which about 487,000 became service requests, against a target of answering 80% of calls within 75 seconds. These come from the operator's own report to committee, not from the open dataset.

Descriptive only — not page/paragraph exact
Claims linked
Background source; no baseline claim points here
Open311 GeoReport v2 server directory — Toronto entry wiki.open311.org · background

Open original source ↗

Stable source ID
src-c8e33878752dbdb4
Publisher
Name not classified · wiki.open311.org
Type / language
web-page · language not classified
Published
Not recorded
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

Registration record: jurisdiction_id 'toronto.ca', base_url 'https://secure.toronto.ca/webwizard/ws/', test_url 'https://secure.toronto.ca/open311test/ws/', version 'georeport-v2', production_ready true. Tested 2026-07-26: the production services list returned HTTP 404 and the test server returned HTTP 404. The discovery document at secure.toronto.ca/open311test/discovery.json still resolves but is dated December 2011.

Descriptive only — not page/paragraph exact
Claims linked
Background source; no baseline claim points here
Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized, full report (17 October 2011) toronto.ca · 4 linked claims

Open original source ↗

Stable source ID
src-d46cedab0edbdd60
Publisher
Name not classified · toronto.ca
Type / language
pdf · language not classified
Published
2011-10-17
Updated
Not recorded
Source last checked
No source-level check date
Record last verified
2026-11-03
Dossier created
2026-11-04
Retrieved copy
No local capture recorded
Archive
No archived copy linked
Content hash
No captured content hash
Locator
Open the recorded source note

The full audit report (Appendix 1). Section B.2 records that during the audit in March 2011 the online status of a request showed only 'open' or 'closed', and that 'closed' did not necessarily mean the service had been provided: it could also mean an investigation had been initiated with service pending, or that service could not be provided for operational reasons. Staff added further status categories in June 2011; Recommendation 3 asks for 'accurate and clear status information on-line'.

Descriptive only — not page/paragraph exact
Claims linked
Known limits of this file
  • Publisher names and source languages have not yet been classified; domains are recorded without guessing.
  • Existing source notes are descriptive locators, not page- or paragraph-exact citations.
  • A missing archive, publication date or content hash is shown as null rather than inferred.
  • The project-level evidence grade ranks the strongest source in the entry; it is not a truth score for every claim.

Continue exploring

Compare this project

🇺🇸 DC 311 and the Open311 API It Started · Washington D.C. D.C. wrote the Open311 standard and its endpoint no longer answers; Toronto's registered endpoint returns 404 as well. 🇺🇸 Miami 311: A County Line and a City Record That Stops in 2024 · Miami Miami's extract carries a goal in days, days taken and an overdue flag; Toronto's has a status field and no closure date at all. 🇨🇦 Toronto Open Data: CKAN portal under a bespoke municipal licence · Toronto The yearly request archives sit in the city's CKAN catalogue — the same catalogue whose bespoke licence only 115 of 554 records name.

Explore the wider context

🗺️ Your City's Problem Map Is Really a Map of Who Complains📖 Civic participation platform📖 Digital identity📖 Government super-app
📎 Cite this project

1001 Smart Cities (2026). “311 Toronto: Service Requests, Open Data and Service Standards” — Toronto, Canada. The Smart City Atlas. https://1001smartcities.org/projects/toronto-311/ (last verified 2026-11-03). Data: CC BY 4.0.

The underlying data is free to reuse with attribution — see the open data page.

🚩 Report an error · 🔔 Follow changes to this entry (RSS)

✉️ One source-checked project a week. No pitches, no vendors.

Inside: the Landmark of the Week, one Insight, the newly documented cities. One-click unsubscribe. About the newsletter · RSS