SourceFinch Verified · Company registries
Public Notices
Recent records from Public Notices on data.winnipeg.ca: up to 1,000 rows with stable identifiers for change monitoring. Contact columns are excluded.
- Healthy · 100% of observed runs successful
- Company registries
- Winnipeg open data
- data.winnipeg.ca
- Open data portal
- 11 typed fields
Monitor this sourceAPI, CLI, SDK and MCP
What changedNo changes in 7 days
At a glance
- Publisher
- Winnipeg open data · homepage
- Category
- Company registries
- Jurisdiction
- data.winnipeg.ca
- Publisher updates
- Updated by the publisher; typically daily or weekly
- Recommended schedule
- Daily for your monitor; SourceFinch verifies the recipe daily
- Records per run
- 1,000 in the latest run
- Record key
id- Acquired from
- Open data portal:
https://data.winnipeg.ca/resource/gnxp-9hpt.json?$select=notice_id,notice_type,community,address,description,approval_type,meeting_date,decision,in_date,order_date,appeal_date&$limit=1000&$order=notice_id - Recipe
- v1.0.0, approved November 17, 2026
- Version notes
- First Verified version generated 2026-11-17 from batch backlog.
- Verified since
- November 17, 2026
- Last green run
- November 17, 2026
- Changes, last 7 days
- 0 · see what changed
What the data contains
Open data published on data.winnipeg.ca as “Public Notices”. Each daily run reads up to 1,000 rows through the portal's SODA API, naming only non-contact columns. A monitor reports new and changed rows inside the cohort. Leaving the cohort does not establish deletion. SourceFinch is independent of the publisher.
Fields and types
Every record has these fields. The key field id identifies a record across runs, so changes are reported field by field.
| Field | Type | Description |
|---|---|---|
idkey | string | Publisher field `notice_id`. The record key. |
notice_type | string, nullable | Publisher field `notice_type`. |
community | string, nullable | Publisher field `community`. |
address | string, nullable | Publisher field `address`. |
description | string, nullable | Publisher field `description`. |
approval_type | string, nullable | Publisher field `approval_type`. |
meeting_date | datetime, nullable | Publisher field `meeting_date`. |
decision | string, nullable | Publisher field `decision`. |
in_date | datetime, nullable | Publisher field `in_date`. |
order_date | datetime, nullable | Publisher field `order_date`. |
appeal_date | datetime, nullable | Publisher field `appeal_date`. |
Sample output
The first 5 of 1,000 records from SourceFinch's own run on November 17, 2026, exactly as delivered.
| Field | Record 1 | Record 2 | Record 3 | Record 4 | Record 5 |
|---|---|---|---|---|---|
id | 14-133948/C | 15-138139/C | 15-138139/C | 15-138141/C | 15-139852/C |
notice_type | VARIANCE | VARIANCE | APPEAL | CONDITIONAL USE | CONDITIONAL USE |
community | East Kildonan-Transcona | City Centre | City Centre | City Centre | City Centre |
address | 720 Kildare AVE E and 301 Redonda ST | 928 Carter AVE | 928 Carter AVE | 928 Carter AVE | 123 Clare AVE |
description | To vary the "RMF-M" dimensional standards of Zoning By-Law No. 200/2006 for the establishment of three zoning lots as follows: 1) on Proposed Lot 1, the maintenance of an existing assisted living facility to permit no west side yard instead of 10 feet (3.05 metres); 2) on Proposed Lot 2: a) for the maintenance of a multi-family dwelling to permit the following: i) no east side yard instead of 18 feet (5.5 metres); ii) no west side yard instead of 18 feet (5.5 metres); b) for the establishment of an accessory parking area to permit the following: i) a front yard of 7 feet (2.1 metres) instead of 25 feet (7.62 metres); 3) on Proposed Lot 3: a) for the construction of a 5 storey, assisted living facility to permit the following: i) no east side yard instead of 16 feet (4.88 metres); ii) a rear yard of 9.6 feet (2.93 metres) instead of 25 feet (7.62 metres); b) for the establishment of an accessory parking area to permit the following: i) parking stalls having no direct access to an aisle or driveway (access will be by cross-access agreement with adjoining property). | To vary the "R2 PDO Airport Vicinity" dimensional standards of Zoning By-Law No. 200/2006 as follows: 1) for the establishment of two (2) residential zoning lots to permit lot areas of 2,500 square feet (232.3 square metres) instead of 5,000 square feet (464.5 square metres); 2) for the construction of a single-family dwelling, each on Lot 6 and Lot 7, to permit a front yard of 17 feet (5.2 metres) instead of 24 feet (7.3 metres). | To vary the "R2 PDO Airport Vicinity" dimensional standards of Zoning By-Law No. 200/2006 as follows: 1) for the establishment of two (2) residential zoning lots to permit lot areas of 2,500 square feet (232.3 square metres) instead of 5,000 square feet (464.5 square metres); 2) for the construction of a single-family dwelling, each on Lot 6 and Lot 7, to permit a front yard of 17 feet (5.2 metres) instead of 24 feet (7.3 metres). | For a Conditional Use under Zoning By-Law No. 200/2006 to permit the establishment of one (1) secondary suite, attached use accessory to a single-family dwelling residence on each Lot 6 and Lot 7. | For a Conditional Use under Zoning By-Law No. 200/2006 to permit the establishment of a detached secondary suite use. |
approval_type | Meeting | Meeting | Meeting | Meeting | Meeting |
meeting_date | 2016-02-03T00:00:00.000 | 2016-02-11T00:00:00.000 | 2016-02-11T00:00:00.000 | 2016-02-11T00:00:00.000 | 2016-04-20T00:00:00.000 |
decision | Approved with Condition(s) | Approved with Condition(s) | Approved with Condition(s) | Approved with Condition(s) | Approved with Condition(s) |
in_date | 2014-06-16T14:50:38.000 | 2015-06-25T11:46:58.000 | 2015-06-25T11:46:58.000 | 2015-06-25T11:49:55.000 | 2015-07-03T10:17:31.000 |
order_date | 2016-02-08T00:00:00.000 | 2015-12-21T00:00:00.000 | 2015-12-21T00:00:00.000 | 2015-12-21T00:00:00.000 | 2016-04-25T00:00:00.000 |
appeal_date | 2016-02-25T00:00:00.000 | 2016-01-07T00:00:00.000 | — | 2016-01-07T00:00:00.000 | 2016-05-12T00:00:00.000 |
Sample as JSON
[
{
"id": "14-133948/C",
"address": "720 Kildare AVE E and 301 Redonda ST",
"in_date": "2014-06-16T14:50:38.000",
"decision": "Approved with Condition(s)",
"community": "East Kildonan-Transcona",
"order_date": "2016-02-08T00:00:00.000",
"appeal_date": "2016-02-25T00:00:00.000",
"description": "To vary the \"RMF-M\" dimensional standards of Zoning By-Law No. 200/2006 for the establishment of three zoning lots as follows:\n1) on Proposed Lot 1, the maintenance of an existing assisted living facility to permit no west side yard instead of 10 feet (3.05 metres);\n2) on Proposed Lot 2:\n a) for the maintenance of a multi-family dwelling to permit the following:\n i) no east side yard instead of 18 feet (5.5 metres);\n ii) no west side yard instead of 18 feet (5.5 metres);\n b) for the establishment of an accessory parking area to permit the following:\n i) a front yard of 7 feet (2.1 metres) instead of 25 feet (7.62 metres);\n3) on Proposed Lot 3:\n a) for the construction of a 5 storey, assisted living facility to permit the following:\n i) no east side yard instead of 16 feet (4.88 metres);\n ii) a rear yard of 9.6 feet (2.93 metres) instead of 25 feet (7.62 metres);\n b) for the establishment of an accessory parking area to permit the following:\n i) parking stalls having no direct access to an aisle or driveway (access will be by cross-access agreement with adjoining property).",
"notice_type": "VARIANCE",
"meeting_date": "2016-02-03T00:00:00.000",
"approval_type": "Meeting"
},
{
"id": "15-138139/C",
"address": "928 Carter AVE",
"in_date": "2015-06-25T11:46:58.000",
"decision": "Approved with Condition(s)",
"community": "City Centre",
"order_date": "2015-12-21T00:00:00.000",
"appeal_date": "2016-01-07T00:00:00.000",
"description": "To vary the \"R2 PDO Airport Vicinity\" dimensional standards of Zoning By-Law No. 200/2006 as follows:\n1) for the establishment of two (2) residential zoning lots to permit lot areas of 2,500 square feet (232.3 square metres) instead of 5,000 square feet (464.5 square metres);\n2) for the construction of a single-family dwelling, each on Lot 6 and Lot 7, to permit a front yard of 17 feet (5.2 metres) instead of 24 feet (7.3 metres).",
"notice_type": "VARIANCE",
"meeting_date": "2016-02-11T00:00:00.000",
"approval_type": "Meeting"
},
{
"id": "15-138139/C",
"address": "928 Carter AVE",
"in_date": "2015-06-25T11:46:58.000",
"decision": "Approved with Condition(s)",
"community": "City Centre",
"order_date": "2015-12-21T00:00:00.000",
"appeal_date": null,
"description": "To vary the \"R2 PDO Airport Vicinity\" dimensional standards of Zoning By-Law No. 200/2006 as follows:\n1) for the establishment of two (2) residential zoning lots to permit lot areas of 2,500 square feet (232.3 square metres) instead of 5,000 square feet (464.5 square metres);\n2) for the construction of a single-family dwelling, each on Lot 6 and Lot 7, to permit a front yard of 17 feet (5.2 metres) instead of 24 feet (7.3 metres).",
"notice_type": "APPEAL",
"meeting_date": "2016-02-11T00:00:00.000",
"approval_type": "Meeting"
},
{
"id": "15-138141/C",
"address": "928 Carter AVE",
"in_date": "2015-06-25T11:49:55.000",
"decision": "Approved with Condition(s)",
"community": "City Centre",
"order_date": "2015-12-21T00:00:00.000",
"appeal_date": "2016-01-07T00:00:00.000",
"description": "For a Conditional Use under Zoning By-Law No. 200/2006 to permit the establishment of one (1) secondary suite, attached use accessory to a single-family dwelling residence on each Lot 6 and Lot 7.",
"notice_type": "CONDITIONAL USE",
"meeting_date": "2016-02-11T00:00:00.000",
"approval_type": "Meeting"
},
{
"id": "15-139852/C",
"address": "123 Clare AVE",
"in_date": "2015-07-03T10:17:31.000",
"decision": "Approved with Condition(s)",
"community": "City Centre",
"order_date": "2016-04-25T00:00:00.000",
"appeal_date": "2016-05-12T00:00:00.000",
"description": "For a Conditional Use under Zoning By-Law No. 200/2006 to permit the establishment of a detached secondary suite use.",
"notice_type": "CONDITIONAL USE",
"meeting_date": "2016-04-20T00:00:00.000",
"approval_type": "Meeting"
}
]Evidence behind every value
- Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash
d23bc05b1d217613b22a279ec87e03c3b37223b7edd9fe84ff967c76061aa3a6. - Every value records where it came from in that response: a JSON Pointer into the retained capture.
- Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is
6d2092dabf63abbd369d7cb345146dbbe02c24366ac303874867a6e468dcd9a8, timestamped November 17, 2026. - The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
- Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch:
sourcefinch verify-bundle run.wacz.
Terms posture and usage rights
- Terms
- Automated access permitted · publisher's terms
- robots.txt
- Allows this path · SHA-256
59a49c0fe1a720e4… - AI-preference signals
- None observed at review
- Public record
- Yes. Municipal/state open data portal dataset gnxp-9hpt on data.winnipeg.ca.
- Reviewed
- November 17, 2026; next review May 17, 2027
- Licence basis
- Publisher's terms of use
- Commercial use
- Allowed
- Redistribution
- Allowed
- Attribution
- Required (text below)
Published on the data.winnipeg.ca open data portal for public use. Anonymous SODA API access needs no key. Portal robots.txt typically allows /resource/ with a crawl delay. Contact-name columns are not requested by this recipe.
Winnipeg open data (data.winnipeg.ca). SourceFinch is independent of the publisher.
Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.
Reliability
- Runs, last 30 days
- 1
- Green
- 100%
- Failed
- 0
- Median run time
- 3.7 s
- Latest run
- success, November 17, 2026
Measured on completed runs of this recipe version across SourceFinch, anonymized, within a rolling 30-day window. First successful observation: November 17, 2026. A new recipe has only the history collected since that date; this is not a 30-day uptime guarantee.
Use it
Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).
Console
Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.
Portable recipe
Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.
{
"schema": "sourcefinch/source@1",
"name": "Public Notices",
"url": "https://data.winnipeg.ca/resource/gnxp-9hpt.json?$select=notice_id,notice_type,community,address,description,approval_type,meeting_date,decision,in_date,order_date,appeal_date&$limit=1000&$order=notice_id",
"recipe": {
"mode": "http",
"format": "json",
"items": "[*]",
"fields": {
"id": "notice_id",
"address": "address",
"in_date": "in_date",
"decision": "decision",
"community": "community",
"order_date": "order_date",
"appeal_date": "appeal_date",
"description": "description",
"notice_type": "notice_type",
"meeting_date": "meeting_date",
"approval_type": "approval_type"
},
"required": [
"id"
],
"types": {
"appeal_date": "datetime",
"in_date": "datetime",
"meeting_date": "datetime",
"order_date": "datetime"
}
},
"schedule": "daily",
"key_field": "id"
}source.json
The request body used by the API, CLI and SDK examples.
{
"name": "Public Notices",
"url": "https://data.winnipeg.ca/resource/gnxp-9hpt.json?$select=notice_id,notice_type,community,address,description,approval_type,meeting_date,decision,in_date,order_date,appeal_date&$limit=1000&$order=notice_id",
"recipe": {
"mode": "http",
"format": "json",
"items": "[*]",
"fields": {
"id": "notice_id",
"address": "address",
"in_date": "in_date",
"decision": "decision",
"community": "community",
"order_date": "order_date",
"appeal_date": "appeal_date",
"description": "description",
"notice_type": "notice_type",
"meeting_date": "meeting_date",
"approval_type": "approval_type"
},
"required": [
"id"
],
"types": {
"in_date": "datetime",
"order_date": "datetime",
"appeal_date": "datetime",
"meeting_date": "datetime"
}
},
"key_field": "id",
"schedule": "daily",
"rights": true,
"catalog": {
"slug": "winnipeg-public-notices",
"version_id": "4385cee0-1305-4e4f-87e5-a7009d1020ab"
}
}REST API
Create an API key under Console → API keys. Reference: /docs/api.
# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/winnipeg-public-notices -H "Authorization: Bearer $SOURCEFINCH_API_KEY"
# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
-H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d @source.json
# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
-H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
-H "Idempotency-Key: $(uuidgen)"CLI
The sourcefinch CLI is not on npm yet; see /docs/cli.
sourcefinch login
sourcefinch catalog get winnipeg-public-notices --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_IDTypeScript SDK
The SDK is not on npm yet; see /docs/sdk.
import { SourceFinch } from "@sourcefinch/sdk";
const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("winnipeg-public-notices");
const source = await sf.sources.create({
catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
name: entry.name.slice(0, 100),
url: entry.acquisition_path.endpoint,
recipe: entry.recipe.definition,
key_field: entry.recipe.key_field,
schedule: entry.recipe.schedule,
rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);MCP
Remote MCP server with OAuth; see /docs/mcp.
claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp
# then ask your agent:
"Use SourceFinch to monitor Public Notices: get_catalog_source winnipeg-public-notices,
then create_source with its create_source_args (dry run first), then run_source."Pricing
Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.
Related sources
More from Winnipeg open data and in company registries.
SourceFinch is independent and is not affiliated with or endorsed by Winnipeg open data. This page describes public notices as SourceFinch acquires it.