SourceFinch Verified · Building Permits

Infill Compliance Team Data Dashboard_Development Permit Inspectors

Recent records from Infill Compliance Team Data Dashboard_Development Permit Inspectors on data.edmonton.ca: up to 1,000 rows with stable identifiers for change monitoring. Contact columns are excluded.

Monitor this sourceAPI, CLI, SDK and MCP

What changed

At a glance

Jurisdiction
data.edmonton.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.edmonton.ca/resource/2mim-xdmj.json?$select=row_id,date,type,inspection_date_1,inspection_result_1,action_taken_1&$limit=1000&$order=row_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

What the data contains

Open data published on data.edmonton.ca as “Infill Compliance Team Data Dashboard_Development Permit Inspectors”. 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.

FieldTypeDescription
idkeystringPublisher field `row_id`. The record key.
datedatetime, nullablePublisher field `date`.
typestring, nullablePublisher field `type`.
inspection_date_1string, nullablePublisher field `inspection_date_1`.
inspection_result_1string, nullablePublisher field `inspection_result_1`.
action_taken_1string, nullablePublisher field `action_taken_1`.

Sample output

The first 5 of 1,000 records from SourceFinch's own run on November 17, 2026, exactly as delivered.

FieldRecord 1Record 2Record 3Record 4Record 5
idIC000000000000IC100076802900IC100253965000IC100263333800IC100422779000
date2017-07-28T00:00:00.0002019-08-01T00:00:00.0002017-03-07T00:00:00.0002017-03-07T00:00:00.0002017-03-13T00:00:00.000
typeHouse ComboHouse ComboHouse ComboHouse ComboHouse Combo
inspection_date_112/1/20183/1/20185/1/20186/1/20181/1/2019
inspection_result_1Final PassedInitial PassedInitial PassedInitial PassedFinal Passed
action_taken_1NoneNoneNoneNoneNone
Sample as JSON
[
  {
    "id": "IC000000000000",
    "date": "2017-07-28T00:00:00.000",
    "type": "House Combo",
    "action_taken_1": "None",
    "inspection_date_1": "12/1/2018",
    "inspection_result_1": "Final Passed"
  },
  {
    "id": "IC100076802900",
    "date": "2019-08-01T00:00:00.000",
    "type": "House Combo",
    "action_taken_1": "None",
    "inspection_date_1": "3/1/2018",
    "inspection_result_1": "Initial Passed"
  },
  {
    "id": "IC100253965000",
    "date": "2017-03-07T00:00:00.000",
    "type": "House Combo",
    "action_taken_1": "None",
    "inspection_date_1": "5/1/2018",
    "inspection_result_1": "Initial Passed"
  },
  {
    "id": "IC100263333800",
    "date": "2017-03-07T00:00:00.000",
    "type": "House Combo",
    "action_taken_1": "None",
    "inspection_date_1": "6/1/2018",
    "inspection_result_1": "Initial Passed"
  },
  {
    "id": "IC100422779000",
    "date": "2017-03-13T00:00:00.000",
    "type": "House Combo",
    "action_taken_1": "None",
    "inspection_date_1": "1/1/2019",
    "inspection_result_1": "Final Passed"
  }
]

Evidence behind every value

  • Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash 1c30949472e51b51418569a75a59cc08517091b13a9e91d0b461d55b7940fcc4.
  • 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 500179376165b2f75aaee48d4a0257a00d138608daf2b3549bb34290a2fa1bea, 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 08de0c58981b7fba…
AI-preference signals
None observed at review
Public record
Yes. Municipal/state open data portal dataset 2mim-xdmj on data.edmonton.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.edmonton.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.

Edmonton open data (data.edmonton.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.6 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": "Infill Compliance Team Data Dashboard_Development Permit Inspectors",
  "url": "https://data.edmonton.ca/resource/2mim-xdmj.json?$select=row_id,date,type,inspection_date_1,inspection_result_1,action_taken_1&$limit=1000&$order=row_id",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "id": "row_id",
      "date": "date",
      "type": "type",
      "action_taken_1": "action_taken_1",
      "inspection_date_1": "inspection_date_1",
      "inspection_result_1": "inspection_result_1"
    },
    "required": [
      "id"
    ],
    "types": {
      "date": "datetime"
    }
  },
  "schedule": "daily",
  "key_field": "id"
}

source.json

The request body used by the API, CLI and SDK examples.

{
  "name": "Infill Compliance Team Data Dashboard_Development Permit Inspectors",
  "url": "https://data.edmonton.ca/resource/2mim-xdmj.json?$select=row_id,date,type,inspection_date_1,inspection_result_1,action_taken_1&$limit=1000&$order=row_id",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "id": "row_id",
      "date": "date",
      "type": "type",
      "action_taken_1": "action_taken_1",
      "inspection_date_1": "inspection_date_1",
      "inspection_result_1": "inspection_result_1"
    },
    "required": [
      "id"
    ],
    "types": {
      "date": "datetime"
    }
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "edmonton-infill-compliance-team-data-dashboard-development-permit-inspectors",
    "version_id": "18a961d6-e607-4700-9578-82b1b21322e4"
  }
}

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/edmonton-infill-compliance-team-data-dashboard-development-permit-inspectors -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 edmonton-infill-compliance-team-data-dashboard-development-permit-inspectors --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

TypeScript 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("edmonton-infill-compliance-team-data-dashboard-development-permit-inspectors");
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 Infill Compliance Team Data Dashboard_Development Permit Inspectors: get_catalog_source edmonton-infill-compliance-team-data-dashboard-development-permit-inspectors,
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.

More from Edmonton open data and in building permits.

SourceFinch is independent and is not affiliated with or endorsed by Edmonton open data. This page describes infill compliance team data dashboard_development permit inspectors as SourceFinch acquires it.