Archiving Real Estate Listings Before They're Delisted

A property listing is temporary by design. The moment a unit sells, a lease is signed, or an agent pulls a stale listing, the page comes down — photos, price history, and description included. For brokerages, appraisers, investors tracking a market, and anyone who needs to reference "what was this listed for and when," that page disappearing is a real loss, not just an inconvenience.

A scheduled screenshot, taken while the listing is still live, turns that disappearing page into a permanent, dated record.

Why This Comes Up Often

• Price history disputes. A listing that got relisted at a different price is easier to prove with a dated screenshot than a memory of what it used to say.
• Market research and comps. Appraisers and investors tracking comparable properties lose access to the original listing the moment it's marked sold.
• Client records for brokerages. Agents often want a permanent record of exactly what was marketed, including photos and description, independent of the listing platform's own retention policy.
• Portfolio tracking. Property managers watching a set of listings across multiple platforms benefit from one consistent archive format instead of screenshots taken manually and inconsistently.

Capturing a Listing Page

curl --request POST \
  --url https://api.prod.ss.snapshot-site.com/api/v1/screenshot \
  --header 'Content-Type: application/json' \
  --header 'x-snapshotsiteapi-key: YOUR_API_KEY' \
  --data '{
    "url": "https://example-listings-site.com/property/12345",
    "format": "png",
    "width": 1440,
    "fullSize": true,
    "hideCookie": true
  }'

fullSize: true matters here — listing pages usually carry the full photo gallery, price, and description below the fold, and a partial capture is not a useful record if it cuts off before the price or key details.

Building a Simple Watch List

The practical setup is a spreadsheet or small database of listing URLs worth tracking, plus a scheduled job that captures each one on a recurring basis (daily is usually enough; listings don't change minute to minute). Store the resulting image alongside the listing's address, the capture date, and the source URL — that triplet turns a folder of screenshots into something searchable later.

Detecting Price Changes, Not Just Archiving

A static archive answers "what did this look like on this date." To catch a price change or a relisting as it happens, compare each new capture against the previous one with v3/compare:

curl --request POST \
  --url https://api.prod.ss.snapshot-site.com/api/v3/compare \
  --header 'Content-Type: application/json' \
  --header 'x-snapshotsiteapi-key: YOUR_API_KEY' \
  --data '{
    "before": {"imageUrl": "https://cdn.example.com/archive/12345-2025-07-13.png"},
    "after": {"url": "https://example-listings-site.com/property/12345", "width": 1440, "fullSize": true, "hideCookie": true},
    "threshold": 0.1
  }'

A meaningful mismatchPercentage is worth a manual look — the price section, photo count, or status badge may have changed since the last capture.

Knowing When a Listing Comes Down

A listing that gets pulled will start returning a different page — a 404, a redirect to a search results page, or a "this listing is no longer available" message. Rather than treating that as a failure, treat it as a signal: the last successful capture before that point is the final archived state of the listing, and the watch list entry can be retired at that point.

For anyone tracking property listings at any real volume, Snapshot Site turns a manual "grab a screenshot before it's gone" habit into something that happens automatically in the background.