A New York commercial real estate platform
Keeps its market coverage complete with listing data from Import.io.
Every listing, every price cut, every permit. Resolved to the property, not the portal.
Import.io collects residential and commercial listings, price changes, rents, days on market and building permits from property portals and public sources. Property, investment and research teams receive property-resolved records with listing history through an API or managed feed.
| Property | Portals | List price | Δ | Days on market | $/sq ft | Status |
|---|---|---|---|---|---|---|
| 1420 Oak St | 3 | $689,000 | −$20,000 | 41 | $412 | active |
| 88 Riverside Dr #4B | 2 | $415,000 | — | 12 | $498 | active |
| 3107 Cedar Ln | 3 | $529,900 | −$15,100 | 63 | $356 | price cut |
| 912 W 34th St | 1 | $1,250,000 | — | 4 | $611 | new |
| 4400 Lamar Blvd #210 | 2 | $2,450 /mo | +$50 | 9 | $2.18 | rental |
| 7719 Mesa Dr | 3 | $742,000 | — | 28 | $389 | pending |
Production examples from organisations using Import.io today and in recent years.
Keeps its market coverage complete with listing data from Import.io.
Runs a managed collection program across its listing sources.
Has used Import.io for market and listing data.
The same home appears on three portals with three prices, two sets of photos and a status that lags by a week. The value isn’t in any one listing — it’s in resolving them to the property and keeping the history. Import.io does that across listings, rentals and the permits that show where supply is heading.
Portals syndicate, agents relist, statuses lag and photos repeat. Counting listings overstates supply; reading one portal misses the price cut on another. Anyone building a valuation model, a market report or an acquisition screen needs the same thing: one record per property with its full history.
Permits tell you what’s coming. Thousands of county and city portals publish them in different formats, often as PDFs. We turn them into one dataset alongside the listings, so supply and demand sit in the same table.
Six programs we run most often in this industry.
Related guidance: listings pages, data feeds, data normalization, managed collection versus in-house scraping.
Listings from every portal resolved to the parcel, with one status, one price history and one days-on-market count.
listingsPrice history, cuts and $/sq ft by micro-market as inputs to valuation models and pricing decisions.
valuationAsking rents, concessions and availability by unit type, for yield and affordability analysis.
rentalsBuilding permits by jurisdiction, type and valuation, so new supply shows up months before it lists.
permitsAvailability, asking rents and space types from commercial listing sites.
commercialListings and sales by brokerage and office over time.
market share| field | type | example |
|---|---|---|
| parcel_id | str | 0231-0045-12 |
| address | str | 1420 Oak St, Austin TX 78704 |
| lat / lon | num | 30.2466 / −97.7640 |
| status | enum | active |
| list_price | num | 689000 |
| price_history | list | 709000 → 689000 |
| days_on_market | int | 41 |
| beds / baths | num | 3 / 2 |
| sqft | int | 1,672 |
| portals | list | 3 sources |
| brokerage | str | Riverton Realty |
| retrieved_at | ts | 2026-09-25T06:02:11Z |
What breaks when this is done with scripts, and how Import.io handles it.
Addresses, units and parcels are normalised and matched across portals, so one property is one record.
Status changes are tracked per source and reconciled, so a sale doesn’t show as active for a week on one portal.
Each jurisdiction’s portal and PDF format is handled once and maintained, not rebuilt every quarter.
Every price and status change is versioned from first capture, so price cuts and days on market are facts, not estimates.
A clear operating plan before collection begins.
Agree the public sites, pages and coverage the program needs.
Define the entities, fields and validation rules for each structured record.
Set the refresh schedule and choose API or managed-feed delivery.
Same capture engine underneath each one.
Data and analytics teams who want resolved listings and permits delivered daily to their warehouse.
learn more →US residential listings and construction permits, maintained and ready to trial.
learn more →Analysts who want to build their own market extractors.
learn more →Programs collect publicly displayed listing and public-record information. Agent contact details and owner names can be personal data; they are excluded by default and included only where lawful and required.
Straight answers.
Addresses and units are normalised and matched to the parcel, then listings are merged into one property record with a history from every source.
Yes. Every price and status change is versioned from our first capture, so price cuts and days on market are observed rather than inferred.
Coverage is built per program from the jurisdictions you need; the permits dataset shows current coverage, and new counties are added on request.
Yes. Rental listings with asking rents and concessions, and commercial listings with availability and asking rents.
Yes. Programs run in any market; portals, address formats and public records are handled per country.