Skip to main content
GET
Read what changed on a parcel, week by week
The timeline of one parcel: a list of history events, newest first. Each event carries the week the replay saw it in, and the values before and after. The response also carries a summary and a coverage block per domain.

​
Use it when

The activity feed on a subject property, and any question of the form “when did this change”. Examples: when the owner changed and under which deed, when the listing took a price cut, when the parcel went vacant, when taxes went delinquent.

​
Where the timeline comes from

The replay compares each weekly delivery with the one before it. Where a domain’s columns differ, that is an event. The replay dates the event to the week of the file it saw the change in. Investorlift built the lake from one full delivery. The replay starts at that delivery, meta.coverage[].parcel.history.first_week, so no event is older than that. span_weeks says how many weeks passed since the replay last saw the parcel. It is 1 in a normal week. Across a gap in the deliveries, the replay dates the change to the first file after the gap. It sets span_weeks to the length of the gap. The replay invents no intermediate week, and it dates no event to a week with no delivery. So an owner change with span_weeks: 5 occurred at some point in those five weeks, not on the week the event carries.

​
Read the response

  • domains filters the events and since cuts them off at a week. The domains are ownership, mailing, occupancy, vacancy, classification, structure, assessment, tax, sale, deed, listing, owner_profile, valuation and financing.
  • coverage is per domain, { first_week, last_week }. It answers the question “why is there nothing here”. Valuation and financing events stop at the slice date. The market’s coverage row names it in meta.coverage[].parcel.financing.as_of. The deliveries after that date carry neither dataset. The other domains run to the last week replayed.
  • before and after are the domain’s own columns, keyed as the delivery names them. before is null on a first sighting and after is null on a deletion. On an owner_change the deed object carries the deed the same week showed: its document type, its price and its recording date.
  • summary is the block the search filters read. It holds owner changes in three years, the last owner change, listing cycles in a year, and price cuts on the current listing. It also says since when the parcel is vacant or delinquent.

​
Gotchas

  • Only the ZIP codes the history lake covers have a timeline. A parcel outside them answers 422 history_unavailable, which names the ZIPs the lake does cover. The same ZIPs are in meta.coverage[].parcel.history.zips. Counties, cities and ZIP codes lists them.
  • valuation and financing events come from the dated snapshot, so a response that carries them also carries meta.dated[]. See dated data.
  • A week with no event is not in the list. The list is events, not a calendar.
  • The API answers 404 not_found when the parcel is in no market with parcel tables. It answers 422 parcels_unavailable when the market has none.

Authorizations

​
Authorization
string
header
required

API key from the developer console (starts with zpka_). Create one at https://developers.investorlift.com/get-a-key.

Path Parameters

​
property_id
string
required

Parcel id, prop_<32 hex>, from /v1/properties/resolve or any deal's property.id. The prefix is part of the id (400 invalid_id otherwise).

Required string length: 1 - 64

Query Parameters

​
domains
enum<string>[]

Keep events of these domains only (comma list or repeated key).

Minimum array length: 1

The domain of the weekly file an event comes from.

Available options:
ownership,
mailing,
occupancy,
vacancy,
classification,
structure,
assessment,
tax,
sale,
deed,
listing,
owner_profile,
valuation,
financing
​
since
string

Keep events seen in this week or later, YYYY-MM-DD.

​
limit
integer
default:200

Page size, 1-500 (default 200).

Required range: 1 <= x <= 500

Response

The history of one parcel.

The history of one parcel.

​
data
object
required

GET /v1/properties/{id}/history: what changed on the parcel, week by week, since the history lake began.

​
meta
object
required

Response metadata: when the API produced it, which markets it covers, and how fresh they are.