CRE Monitor: New Listings and Price Drops on Crexi and LoopNet avatar

CRE Monitor: New Listings and Price Drops on Crexi and LoopNet

Pricing

from $0.40 / 1,000 listing checkeds

Go to Apify Store
CRE Monitor: New Listings and Price Drops on Crexi and LoopNet

CRE Monitor: New Listings and Price Drops on Crexi and LoopNet

Commercial real estate saved-search monitor for Crexi and LoopNet. Get only what changed since your last run: new listings, price drops, price increases, status changes and removed or sold listings. No login. Export CSV, Excel, JSON, XML.

Pricing

from $0.40 / 1,000 listing checkeds

Rating

0.0

(0)

Developer

ParseForge

ParseForge

Maintained by Apify Partner

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Features

Limited permissions

Share

ParseForge

CRE Monitor: New Listings and Price Drops on Crexi and LoopNet

Save a commercial real estate search once and hear only about what changed: new listings, price drops, price increases, status changes and listings that were removed or sold. The first run records a baseline and reports nothing. Every later run compares the search with the last one and returns one row per change. No login, no cookies.

Re-scraping a whole market every morning and diffing spreadsheets by hand is slow and expensive. This Actor keeps the memory for you in a Key-Value Store of your own account, so a scheduled run costs a fraction of a full export and the output is already the list of things worth acting on.

Who uses itWhat they watch for
Acquisition teams and investorsPrice drops on office, retail or industrial assets in a target city
BrokersNew competing listings in a submarket the day they appear
Lenders and appraisersListings that went under contract or were pulled
Market analystsPrice cuts as a pressure signal, with the size of each cut
Alert buildersA clean change feed for Slack, email or a CRM through a webhook

What it does

  • 🆕 New listings: a listing that was not in the last full read of your search.
  • 📉 Price drops and 📈 price increases: previous price, new price, change in dollars and in percent.
  • 🔄 Status changes: for example On-Market to Under Contract (Crexi publishes the status).
  • 🏁 Removed or sold: reported only after the listing is missing from two full reads in a row (you can change that), so one bad page never creates a false sale.
  • 🧠 Memory between runs: the last state of each saved search lives in a named Key-Value Store (cre-monitor-state by default). Keep the name and the search the same and the monitor carries on where it stopped.
  • 🧾 Run summary: a RUN_SUMMARY record says how many listings were read, whether the whole search was covered, and whether the run was a baseline or a comparison.

💡 Why it matters: the page you read this on does not need a human. Put the Actor on a daily schedule and a webhook, and your team only sees listings that moved.

How a run behaves

SituationResult
First run of a searchBaseline saved, no change events, no change charges
Next run, nothing changedSucceeded, 0 rows
Something changedOne row per change, eventId on each one
Search has no listingsSucceeded, 0 rows, a clear message
Invalid input (state, city, type, price range, store name)Succeeded, 0 rows, a message that says what to fix, nothing is read
The site blocks the Actor on every tryThe run is marked Failed and no change is charged
Two runs of the same search at onceEach change is reported once; a run that lost the race says so and charges nothing

Sources and filters

FilterCrexiLoopNet
State and cityyes (city is matched exactly)yes (dallas-tx style search page)
Property typesOffice, Retail, Industrial, Land, Multifamily, Hospitality, Special Purpose, Mixed Use, Self StorageOffice, Retail, Industrial, Land, Multifamily, Hospitality, Flex, Special Purpose, Health Care
Price rangeyes (sale)yes (sale, applied after reading)
For leasenot availableyes
Largest search one run can read1,499 listings1,000 listings

Both sites are read the same way the Commercial Real Estate Listings Scraper (Crexi) and the LoopNet Scraper read them, so this Actor adds no new access method.

⚠️ Keep the search small enough to read in full. "New" and "removed" are only trustworthy when the whole search fits under maxItems. If the search is bigger (Texas office has thousands), price and status changes are still reported, but new and removed listings are held back and the summary says scanComplete: false. Narrow it by city, type or price range.

What a row looks like

FieldMeaning
🏷 eventTypenew_listing, price_drop, price_increase, status_change, removed
🌐 source, listingId, urlWhere the listing lives
🏢 title, propertyType, address, city, state, zip, squareFootage, brokerageThe property
💲 price, priceText, previousPrice, priceChange, priceChangePercentPrice movement (negative change = drop)
📌 status, previousStatusStatus movement
🔁 relistedA removed listing that came back
🕒 firstSeenAt, lastSeenAt, detectedAtTimeline
🔑 eventId, searchNameStable change id for de-duplication, and your label
{
"eventType": "price_drop",
"source": "crexi",
"listingId": "2732214",
"title": "Class A Office Building",
"url": "https://www.crexi.com/properties/2732214/class-a-office-building",
"propertyType": "Office",
"address": "100 Main St",
"city": "Dallas",
"state": "TX",
"price": 1450000,
"previousPrice": 1600000,
"priceChange": -150000,
"priceChangePercent": -9.38,
"status": "On-Market",
"detectedAt": "2026-11-14T09:00:12.000Z",
"eventId": "9f3b7c1d2a4e5f60"
}

Input

FieldWhat it does
sourcescrexi, loopnet or both
city, stateThe place. State alone watches the whole state
listingTypefor-sale or for-lease (lease: LoopNet only)
propertyTypesEmpty means all types
minPrice, maxPriceSale price range
maxItemsListings read per source, per run (free plan 50)
stateStoreNameName of the Key-Value Store that keeps the memory
eventTypesWhich changes to report (default all five)
minPriceChangePercentIgnore moves smaller than this; slow drifts still add up
removalConfirmationsFull reads in a row before a listing counts as removed (default 2)
resetBaselineForget the saved state and record a new baseline
searchNameLabel copied onto each event

Changing the place, type, price range or listing type starts a separate saved search with its own baseline. Changing maxItems or the event filters does not.

FAQ

QuestionAnswer
Does the first run cost me change events?No. It records the baseline and reports nothing; you only pay for the listings it checked.
What if a run fails halfway?Changes are written to the saved state before they are delivered and stay pending until they are, so a crash or a spending limit never loses an event.
Can I run several searches?Yes. Each combination of place, type and price range keeps its own state in the same store.
Can I schedule it?Yes. Daily is typical; add a webhook or an integration to push the rows into Slack, email or a CRM.
What happens on a listing that has no price?Price Upon Request listings are tracked for new, removed and status changes. A price that appears or disappears is not reported as a price change.
Is the saved state private?It lives in a named Key-Value Store in your own Apify account.
Are these official feeds?No. The data is public search data; the Actor is unofficial.

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Crexi or LoopNet. It reads publicly available listing data. You are responsible for using it in line with each site's terms and applicable law.