CRE Monitor: New Listings and Price Drops on Crexi and LoopNet
parseforge/cre-new-listing-and-price-drop-monitor
Real estateAutomationLead generation
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.
- Total runs
- 84
- Bookmarked
- 0
- Last modified
- 7 days ago
This scraper was last updated on .
What does the CRE Monitor: New Listings and Price Drops on Crexi and LoopNet return?
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 it | What they watch for |
|---|---|
| Acquisition teams and investors | Price drops on office, retail or industrial assets in a target city |
| Brokers | New competing listings in a submarket the day they appear |
| Lenders and appraisers | Listings that went under contract or were pulled |
| Market analysts | Price cuts as a pressure signal, with the size of each cut |
| Alert builders | A 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-stateby default). Keep the name and the search the same and the monitor carries on where it stopped. - ๐งพ Run summary: a
RUN_SUMMARYrecord 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
| Situation | Result |
|---|---|
| First run of a search | Baseline saved, no change events, no change charges |
| Next run, nothing changed | Succeeded, 0 rows |
| Something changed | One row per change, eventId on each one |
| Search has no listings | Succeeded, 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 try | The run is marked Failed and no change is charged |
| Two runs of the same search at once | Each change is reported once; a run that lost the race says so and charges nothing |
Sources and filters
| Filter | Crexi | LoopNet |
|---|---|---|
| State and city | yes (city is matched exactly) | yes (dallas-tx style search page) |
| Property types | Office, Retail, Industrial, Land, Multifamily, Hospitality, Special Purpose, Mixed Use, Self Storage | Office, Retail, Industrial, Land, Multifamily, Hospitality, Flex, Special Purpose, Health Care |
| Price range | yes (sale) | yes (sale, applied after reading) |
| For lease | not available | yes |
| Largest search one run can read | 1,499 listings | 1,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 saysscanComplete: false. Narrow it by city, type or price range.
What a row looks like
| Field | Meaning |
|---|---|
๐ท eventType |
new_listing, price_drop, price_increase, status_change, removed |
๐ source, listingId, url |
Where the listing lives |
๐ข title, propertyType, address, city, state, zip, squareFootage, brokerage |
The property |
๐ฒ price, priceText, previousPrice, priceChange, priceChangePercent |
Price movement (negative change = drop) |
๐ status, previousStatus |
Status movement |
๐ relisted |
A removed listing that came back |
๐ firstSeenAt, lastSeenAt, detectedAt |
Timeline |
๐ eventId, searchName |
Stable 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
| Field | What it does |
|---|---|
sources |
crexi, loopnet or both |
city, state |
The place. State alone watches the whole state |
listingType |
for-sale or for-lease (lease: LoopNet only) |
propertyTypes |
Empty means all types |
minPrice, maxPrice |
Sale price range |
maxItems |
Listings read per source, per run (free plan 50) |
stateStoreName |
Name of the Key-Value Store that keeps the memory |
eventTypes |
Which changes to report (default all five) |
minPriceChangePercent |
Ignore moves smaller than this; slow drifts still add up |
removalConfirmations |
Full reads in a row before a listing counts as removed (default 2) |
resetBaseline |
Forget the saved state and record a new baseline |
searchName |
Label 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
| Question | Answer |
|---|---|
| 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. |
๐ 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.
What input does the CRE Monitor: New Listings and Price Drops on Crexi and LoopNet accept?
| Field | Type | What it does | Default |
|---|---|---|---|
| sources | array | Sites to watch: "crexi", "loopnet" or both. Each site keeps its own saved state. | ["crexi","loopnet"] |
| city | string | City to watch, for example Dallas. Leave empty to watch a whole state. A city needs its state. | Dallas |
| state | string | US state as a two-letter code (TX) or full name (Texas). | TX |
| listingType | string | "for-sale" or "for-lease". Lease listings come from LoopNet only (Crexi lease search is not available). | for-sale |
| propertyTypes | array | Leave empty for all types. Valid: office, retail, industrial, land, multifamily, hospitality, flex, special-purpose, health-care, mixed-use, self-storage. Flex and health-care exist on LoopNet only; mixed-use and self-storage on Crexi only. | ["office"] |
| minPrice | integer | Sale price floor. Listings without a numeric price are left out when a price range is set. | not set |
| maxPrice | integer | Sale price ceiling. Must not be below the minimum. | not set |
| maxItems | integer | How many listings of the search to read each run. Crexi serves at most 1,499 per search and LoopNet 1,000. A removed or new listing can only be told apart when the whole search fits, so narrow the search (city, type, price) until the total fits under this number. Free plan: 50. | 50 |
| stateStoreName | string | Named Key-Value Store that remembers the last run of each saved search. Keep it the same between runs. 3 to 63 letters, digits or hyphens. | cre-monitor-state |
| searchName | string | Optional label copied onto every event, handy when you run several saved searches into one workflow. | not set |
| eventTypes | array | Leave empty for all. Valid: new_listing, price_drop, price_increase, status_change, removed. Filtered events still update the saved state, they are just not reported or charged. | ["new_listing","price_drop","price_incre |
| minPriceChangePercent | number | 0 reports every change. Small moves below this percent are ignored and the reference price stays, so slow drifts add up and still trigger. | 0 |
| removalConfirmations | integer | A listing is reported removed only after it is missing from this many full reads in a row. 2 avoids false removals from a bad page. | 2 |
| resetBaseline | boolean | Forget the saved state of this search and record a fresh baseline now (no change events this run). | false |
| proxyConfiguration | object | Leave Apify Proxy off (recommended): the Actor reads Crexi directly and only moves to Apify datacenter and then residential addresses if Crexi refuses a request, the same way the LoopNet Scraper does. Turn it on to force a proxy for every Crexi request. LoopNet manages its own egress. | {"useApifyProxy":false} |
How much does the CRE Monitor: New Listings and Price Drops on Crexi and LoopNet cost?
from $0.30 per 1,000 results
| Charged for | What it is | Price each |
|---|---|---|
| Listing checked | Charged once per listing read from Crexi or LoopNet for your saved search, including the first run that records the baseline. Unchanged listings cost only this. | $0.0003 to $0.0006 |
| Change detected | Charged once per change delivered: new listing, price drop, price increase, status change or removed listing. Never charged on the baseline run. | $0.012 to $0.024 |
| Actor Start | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). | $0.015 |
Tiered: the lower figure is the price on a higher Apify plan. Billing and the free credit live on Apify.
How do I call the CRE Monitor: New Listings and Price Drops on Crexi and LoopNet API?
One POST returns the dataset directly. Same shape for every scraper in the library, so swapping the slug is the only change.
curl -X POST "https://api.apify.com/v2/acts/parseforge~cre-new-listing-and-price-drop-monitor/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"sources": [
"crexi",
"loopnet"
],
"city": "Dallas",
"state": "TX",
"listingType": "for-sale",
"propertyTypes": [
"office"
]
}' What example inputs can I use?
Use these inputs to see how a run is configured.
{
"sources": [
"crexi",
"loopnet"
],
"city": "Dallas",
"state": "TX",
"listingType": "for-sale",
"propertyTypes": [
"office"
]
} What do users say about the CRE Monitor: New Listings and Price Drops on Crexi and LoopNet?
No reviews yet. Be the first.
How do I report an issue with the CRE Monitor: New Listings and Price Drops on Crexi and LoopNet?
We build and maintain this scraper, so a problem with it comes to us. Report it on the Apify listing and the thread stays attached to the scraper where the next person can find it: open an issue.
Broken and urgent, or you would rather not post in public? Write to parseforge@protonmail.com and it reaches the people who wrote it.
What related scrapers can I use?
Run CRE Monitor: New Listings and Price Drops on Crexi and LoopNet on Apify All scrapers
