SourceFinch Verified · Recreation

Cambridge Parking Tickets

Recent records from Cambridge Parking Tickets on data.cambridgema.gov: up to 1,000 rows with stable identifiers for change monitoring. Contact columns are excluded.

Monitor this sourceAPI, CLI, SDK and MCP

What changedNo changes in 7 days

At a glance

Category
Recreation
Jurisdiction
data.cambridgema.gov
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.cambridgema.gov/resource/vnxa-cuyr.json?$select=issue_time,ticket_issue_date,violation_description,location,violation_code&$limit=1000&$where=ticket_issue_date IS NOT NULL&$order=ticket_issue_date DESC
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.cambridgema.gov as “Cambridge Parking Tickets”. 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 `issue_time`. The record key.
ticket_issue_datedatetime, nullablePublisher field `ticket_issue_date`.
violation_descriptionstring, nullablePublisher field `violation_description`.
locationstring, nullablePublisher field `location`.
violation_codestring, nullablePublisher field `violation_code`.

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
id19:10:0018:43:0016:30:0016:27:0012:11:00
ticket_issue_date2025-12-31T00:00:00.0002025-12-31T00:00:00.0002025-12-31T00:00:00.0002025-12-31T00:00:00.0002025-12-31T00:00:00.000
violation_descriptionO/T TIMEMETER EXPMETER EXPMETER EXPO/T TIME
locationjames st&mason stjames st&mason stappian wy&garden stappian wy&brattle st75 amherst st&ames st
violation_codeB12A3A3A3B12
Sample as JSON
[
  {
    "id": "19:10:00",
    "location": "james st&mason st",
    "violation_code": "B12",
    "ticket_issue_date": "2025-12-31T00:00:00.000",
    "violation_description": "O/T TIME"
  },
  {
    "id": "18:43:00",
    "location": "james st&mason st",
    "violation_code": "A3",
    "ticket_issue_date": "2025-12-31T00:00:00.000",
    "violation_description": "METER EXP"
  },
  {
    "id": "16:30:00",
    "location": "appian wy&garden st",
    "violation_code": "A3",
    "ticket_issue_date": "2025-12-31T00:00:00.000",
    "violation_description": "METER EXP"
  },
  {
    "id": "16:27:00",
    "location": "appian wy&brattle st",
    "violation_code": "A3",
    "ticket_issue_date": "2025-12-31T00:00:00.000",
    "violation_description": "METER EXP"
  },
  {
    "id": "12:11:00",
    "location": "75 amherst st&ames st",
    "violation_code": "B12",
    "ticket_issue_date": "2025-12-31T00:00:00.000",
    "violation_description": "O/T TIME"
  }
]

Evidence behind every value

  • Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash a534768e1d29eeb1686448a7cd12f6fd8e4da537460a1d692afac4e315a07e69.
  • 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 6441864580d93ae8485914f576f553225d5aa104b26b1478c2ae490044c99451, 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 df50c56e5723a206…
AI-preference signals
None observed at review
Public record
Yes. Municipal/state open data portal dataset vnxa-cuyr on data.cambridgema.gov.
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.cambridgema.gov 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.

Cambridgema open data (data.cambridgema.gov). 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
1.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": "Cambridge Parking Tickets",
  "url": "https://data.cambridgema.gov/resource/vnxa-cuyr.json?$select=issue_time,ticket_issue_date,violation_description,location,violation_code&$limit=1000&$where=ticket_issue_date IS NOT NULL&$order=ticket_issue_date DESC",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "id": "issue_time",
      "location": "location",
      "violation_code": "violation_code",
      "ticket_issue_date": "ticket_issue_date",
      "violation_description": "violation_description"
    },
    "required": [
      "id"
    ],
    "types": {
      "ticket_issue_date": "datetime"
    }
  },
  "schedule": "daily",
  "key_field": "id"
}

source.json

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

{
  "name": "Cambridge Parking Tickets",
  "url": "https://data.cambridgema.gov/resource/vnxa-cuyr.json?$select=issue_time,ticket_issue_date,violation_description,location,violation_code&$limit=1000&$where=ticket_issue_date IS NOT NULL&$order=ticket_issue_date DESC",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "id": "issue_time",
      "location": "location",
      "violation_code": "violation_code",
      "ticket_issue_date": "ticket_issue_date",
      "violation_description": "violation_description"
    },
    "required": [
      "id"
    ],
    "types": {
      "ticket_issue_date": "datetime"
    }
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "cambridgema-cambridge-parking-tickets",
    "version_id": "b01d37df-be97-4b16-905a-5b6512618a5d"
  }
}

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/cambridgema-cambridge-parking-tickets -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 cambridgema-cambridge-parking-tickets --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("cambridgema-cambridge-parking-tickets");
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 Cambridge Parking Tickets: get_catalog_source cambridgema-cambridge-parking-tickets,
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 Cambridgema open data and in recreation.

SourceFinch is independent and is not affiliated with or endorsed by Cambridgema open data. This page describes cambridge parking tickets as SourceFinch acquires it.