Intelligence Desk & Commercial API

GET/v1/parcels/{pin}

Planned parcel record, source dates and links to available assessments, sales, permits and appeals.

GET /api/v1/parcels/{14-digit-pin}
Authorization: Bearer {your-api-key}

{
  "pin": "parcel identifier",
  "address": "published property address",
  "assessed_total": "published assessed value",
  "owner": "entitled taxpayer association",
  "release": "source and release metadata"
}

GET/v1/feeds/appeal-leads

Planned JSON access to the appeal research pool. The current criteria and real sample rows are available on the appeal-firm product page.

GET /api/v1/feeds/appeal-leads?city={town}
Authorization: Bearer {your-api-key}

{
  "feed": "appeal-leads",
  "release_id": "active release identifier",
  "criteria": "documented research screen",
  "rows": "matching parcel records",
  "next": "pagination cursor, if present"
}

GET/v1/sales?since=

Planned access to published sale records across supported towns, with entitled deed parties and source context.

GET /api/v1/sales?since={date}
Authorization: Bearer {your-api-key}

{
  "since": "requested date",
  "rows": "published sales and permitted party fields",
  "next": "pagination cursor, if present",
  "release_id": "active release identifier"
}

GET/v1/owners/{id}/holdings

Planned administrative ownership links. Taxpayer associations are not verified title or proof of beneficial ownership.

GET /api/v1/owners/{entity-id}/holdings
Authorization: Bearer {your-api-key}

{
  "owner_id": "record association identifier",
  "holdings": "parcels linked in the available records",
  "release": "source and release metadata"
}

POST/v1/webhooks

Planned release notifications for an authorized destination. No webhook registration or delivery is available during pre-sale.

POST /api/v1/webhooks
Authorization: Bearer {your-api-key}
Body: authorized URL and requested event types

{
  "event": "release.published",
  "release_id": "published release identifier",
  "published_at": "publication timestamp",
  "cursor": "link to changes, if available"
}

1.Appeal-lead pull for a law firm

Planned API workflow: review a research pool before outreach.

1. 1.1Pull the current list: GET /v1/feeds/appeal-leads. Each row is a matching residential property assessed more than 10% above its peer median, with no recorded appeal from 2024 onward. An assessment increase is a different signal.
2. 1.2For each retained lead, fetch the dossier: GET /v1/parcels/{pin} — prior assessment, sale history and permit record in one call.
3. 1.3Refresh after each data release and review the current filing history. A missing filing does not establish that the owner is unrepresented; published records may lag.

2.Trade-lead sync into a CRM

Planned API workflow: maintain a reviewed territory research list.

1. 2.1Pull GET /v1/feeds/trade-leads — pre-1985 homes with no building matching permit in the available county feed. Coverage varies by town and date; verify municipal records and actual condition.
2. 2.2Upsert into the CRM keyed on pin; map estimated_value and year_built to lead fields.
3. 2.3On each release.published webhook, pull again and close leads that now show permit activity.

3.Portfolio monitoring by webhook

Planned API workflow: review changes in linked records.

1. 3.1Register once: POST /v1/webhooks with "events": ["release.published"].
2. 3.2On delivery, pull GET /v1/sales?since= the prior release date and match grantee against the entities you track.
3. 3.3For each watched owner, GET /v1/owners/{id}/holdings and diff parcel_count against your stored copy.