1. Primary source
Source: City of Toronto, Building Permits – Active Permits. Licence: Open Government Licence – Toronto. BuildRules is independent of the City and is not an approval or certification service.
The record can include active applications, issued permits and multiple revisions of the same project. A data row is not one distinct property, completed renovation or approved new project.
2. Exact aggregation, not interpretation
BuildRules makes read-only calls to the City’s CKAN datastore_search API. A request without filters returns the current overall row count, while selected counts use exact matches on the PERMIT_TYPE and STATUS fields. No text classifier or model estimates a work type.
Reproducible request body
{
"resource_id": "6d0229af-bc54-46de-9c2b-26759b01dd05",
"filters": {
"STATUS": "Permit Issued"
},
"limit": 0
}Send a POST request to https://ckan0.cf.opendata.inter.prod-toronto.ca/api/3/action/datastore_search. The response’s result.total is the count. A supplied total_was_estimated flag triggers an approximate marker.
The statuses we deliberately sample are Application On Hold, Permit Issued, Inspection, Revision Issued. They are not exhaustive, not ranked and should not be summed to estimate all applications or all issued permits.
3. What a timestamp actually means
The visible “checked” date records when BuildRules retrieved the counts. A separately shown City CSV resource modification time comes from the Toronto CKAN catalogue; it is not proof that the datastore API has been synchronized or that every permit record is complete. Queries and the page can remain cached for up to six hours. We do not invent an official data-update date when none has been validated.
If a public source is unavailable, a count is marked unavailable. A partial response does not silently turn missing records into zero. No historical snapshot or user input is combined into current counts.
4. Why we do not claim year-over-year growth
The City’s active register is not a complete permanent historical archive. Closed records eventually leave it. Counting records with old application dates in today’s active dataset cannot reliably reconstruct how many projects started during those years.
A future trend analysis would need an independently validated longitudinal dataset, clear inclusion criteria, consistent reporting delays and an explanation of what changed in the sample. Two totals retrieved on different days are not automatically evidence that construction increased or decreased.
5. What homeowners should do next
Citywide counts cannot establish whether you need a permit or whether previous work at an individual property was legal. Check the exact address and project conditions; use Toronto’s authoritative application-status search for a particular file, and request a Property Information Report for the City’s defined reporting scope.
Check your project conditions or review the City records options.
6. Independent verification and corrections
Selected counts should be checked against the City’s source on the same retrieval day. Automated availability checks do not certify the City’s data. BuildRules has not published a validated longitudinal permit trend, an impact study, or findings from a completed user-research cohort for this page.
We welcome reproducible corrections. Contact BuildRules with the dataset, field, filter and date of an observed discrepancy.