LoopNet Scraper — CRE Listings, Brokers & Deal Intelligence

Collect commercial real estate listings from LoopNet across the United States. Search markets, enrich known properties, export broker and media data, compare deals, and monitor listing changes from one Actor.

Property listings · Prices & cap rates · Building facts · Broker contacts · Photos & tours · Deal calculations · Change monitoring

What can this Actor do?

Workflow	Use it for	Result
SEARCH	Fast market research	Listing cards with location, asking terms, property type, available space, brokers, photos, and rank
LISTING_DETAILS	Enrich known URLs or IDs	Full property description, facts, brokers, media, source flags, and deal calculations
SEARCH_FULL	Build a complete research dataset	Search discovery followed by full details for every selected listing
MONITOR	Recurring market tracking	New, updated, unchanged, and safely detected removed listings

Popular use cases

• Build commercial property datasets by city, state, property type, or deal type.
• Find offices, retail, industrial, land, multifamily, hospitality, and specialty properties.
• Compare asking prices, lease rates, cap rates, NOI, size, and price per square foot.
• Create broker and brokerage lead lists.
• Download property photos, videos, tours, and brochures when available.
• Track price and status changes across scheduled runs.
• Feed CRE data into spreadsheets, dashboards, CRMs, and AI workflows.

Quick start

Search by location

{
  "mode": "SEARCH",
  "locations": ["Los Angeles, CA"],
  "dealType": "FOR_LEASE",
  "propertyType": "OFFICE",
  "maxItems": 25,
  "maxPages": 1
}

Use a LoopNet search URL

{
  "mode": "SEARCH_FULL",
  "searchUrls": [
    {
      "url": "https://www.loopnet.com/search/office-space/los-angeles-ca/for-lease/"
    }
  ],
  "maxItems": 10,
  "maxPages": 1
}

Enrich listings by ID

{
  "mode": "LISTING_DETAILS",
  "listingIds": [
    "31948105"
  ],
  "maxItems": 1
}

Monitor a market

{
  "mode": "MONITOR",
  "locations": ["Austin, TX"],
  "dealType": "FOR_SALE",
  "propertyType": "INDUSTRIAL",
  "maxItems": 100,
  "maxPages": 5,
  "emitUnchanged": false,
  "emitRemoved": true
}

What data will you receive?

Listing identity

listingId, requestedListingId, listingIdWasResolved, propertyId, listingKey, lrId, listingName, listingUrl, listingType, dealType, status, exposure, dateModified, scrapedAt.

requestedListingId and listingIdWasResolved make redirects explicit when an older listing ID points to a current listing record.

Address and coordinates

streetAddress, city, state, postalCode, county, country, countryCode, cityState, latitude, longitude, locationInterpretation.

Pricing and financials

price, priceText, priceCurrency, pricePerSqFt, capRate, noi, saleType, saleCondition, availableSpace, buildingInfo.

Property facts

propertyType, propertySubtype, propertyTypeId, buildingClass, buildingSize, lotSize, spaceCount, availableSpacesCount, yearBuilt, stories, tenancy, zoning, parkingRatio, frontage, buildingFar, walkScore, factsJson, availableSpacesJson.

Marketing information

description, executiveSummary, highlights, amenities, breadcrumbNames, linksJson.

Brokers and companies

brokerCount, brokerNames, brokerTitles, brokerPhones, brokerEmails, brokerCompanies, brokerProfileUrls, brokerProfileIds, brokerBios, brokerAvatars, brokerCompanyLogos, brokersJson, company, provider.

Contact fields are conditional. If LoopNet does not publish a phone, email, biography, or company value for a listing, it remains empty.

Photos, tours, and documents

coverPhotoUrl, imageCount, imageUrls, imageAlts, videoCount, videoUrls, videoThumbnails, matterportTourUrls, brochureUrls, brochureLabels, mediaJson.

Location intelligence

Depending on the listing, output can include walk, transit, bike, and drive scores; nearby transit, rail, and airport information; traffic counts; points of interest; and demographic blocks.

Fields include walkScore, transitScore, bikeScore, driveScore, score descriptions, nearestTransitDistance, nearestRailDistance, nearestAirportDistance, trafficCount, maxTrafficVolume, nearestTrafficDistance, transportationJson, trafficCountsJson, pointsOfInterestJson, demographicsJson, and dataPointsJson.

Taxes and listing flags

parcelNumber, landAssessment, improvementAssessment, totalAssessment, isActive, isAuction, isSaleDataLocked, listingAcl, ldpAcl, ldpExposure, ldpGroup, ldpPropertyType, ldpStatus, ldpType, flagsJson, profileStateJson.

Complete source coverage

Keep includeRawSource: true to retain conditional source fields in rawSourceJson and the dedicated *Json columns. This is useful when different property types publish different fact, media, broker, transportation, or financial structures.

Deal Intelligence

The Actor adds clear calculations when the required values are available:

• pricePerBuildingSqFtCalculated — asking price divided by building size;
• pricePerLotAcreCalculated — asking price divided by lot acreage;
• estimatedNoiFromCapRate — asking price multiplied by the published cap rate;
• brokerCount, imageCount, hasVideo, hasMatterport, hasBrochure;
• listingCompletenessPercent;
• dataCoverage and missingFieldGroups.

Calculated values are explicitly named and stay empty when their inputs are unavailable.

Monitoring output

The first matching monitoring run establishes a snapshot and returns records as NEW. Later runs can add:

• changeStatus: NEW, UPDATED, UNCHANGED, or REMOVED;
• firstSeenAt, lastSeenAt;
• previousPrice, priceChange, priceChangePercent;
• previousStatus, statusChanged;
• closeStatus, closeDetectedAt.

Removed records are emitted only after an exhaustive source scan. Page, result, source, or budget limits prevent removal detection for that run, avoiding false alerts.

Filters

Input	Purpose
dealType	For sale, for lease, or auction searches
propertyType	Office, retail, industrial, land, multifamily, hospitality, healthcare, and more
minPrice, maxPrice	Filter normalized asking prices
minBuildingSize, maxBuildingSize	Filter building square footage
minCapRate, maxCapRate	Filter published cap rates
maxItems	Total successfully saved unique records
maxPages	Maximum pages per search source

Listings missing a value cannot pass a filter that requires that value. Filtered, duplicate, failed, and unchanged monitoring candidates do not consume maxItems.

Output views

Every run provides focused tables:

View	Designed for
Listings	Core property research
Financials	Prices, cap rates, NOI, and deal ratios
Brokers	Contacts and brokerage research
Media	Photos, videos, tours, and brochures
Location intelligence	Coordinates, access, transport, and traffic
Monitoring	New, changed, unchanged, and removed listings
Run summary	Saved counts, warnings, and stop reasons

Export and integrations

Download data as JSON, JSONL, CSV, Excel, XML, RSS, or HTML Table. Access results through the Apify API or connect the Actor to Google Sheets, Google Drive, Make, Zapier, Slack, Airbyte, webhooks, CRMs, and your own applications.

Save an input as an Apify task to reuse the same market search or monitoring configuration.

Performance

The tested Search workflow collected 50 unique US listings in 8.9 seconds on 512 MB, including two result pages and dataset writes. Full-detail speed depends on the number of selected listings and the amount of media and property data available.

Cost control

For an inexpensive first run:

1. Select SEARCH.
2. Use one location or search URL.
3. Set maxItems to 5–10.
4. Inspect the fields you need.
5. Use LISTING_DETAILS or SEARCH_FULL for the selected properties that need enrichment.

Set Maximum charge per run in Apify Console to create a hard budget ceiling.

Frequently asked questions

Can I paste a complete LoopNet search URL?

Yes. Filters included in a LoopNet /search/ URL are preserved. Location and dropdown filters are used when the Actor builds the search URL for you.

Can I combine URLs and listing IDs?

Yes, in LISTING_DETAILS. Repeated listing IDs are deduplicated before collection.

Why do some listings contain more fields than others?

Land, office, retail, portfolio, auction, lease, and for-sale listings publish different information. Missing values remain empty, while available source blocks can be retained in the JSON columns.

Will filtering reduce the requested result allowance?

No. Filtered and duplicate candidates do not consume maxItems.

Can monitoring report false removals after a short run?

No. Removal detection requires a complete source scan and is disabled for limited or interrupted runs.

Are missing broker contacts estimated?

No. Broker contact values are saved only when they are available for the listing.

How do I call the Actor from code?

Open the API tab for ready-to-copy Python, JavaScript, CLI, HTTP, OpenAPI, and MCP examples.

Support

When reporting an issue, include the run ID, mode, sanitized input, and one affected LoopNet URL or listing ID. This makes the problem quick to reproduce.