Furnished Finder Corporate Housing Scraper

---

🎯 What this scrapes

FurnishedFinder.com lists 30+ day furnished corporate-housing rentals for traveling nurses, corporate relocations, and remote workers. This Actor calls the site's own public GraphQL search API directly — by city/state or a custom map bounding box — and works around its hard 50-result-per-viewport cap with recursive quadrant tiling, so a dense metro like Austin or Houston doesn't get silently truncated at page one.

🔥 What we handle for you

• 🗺️ Recursive quadrant tiling — automatically splits a dense metro's map viewport into quadrants to work around FurnishedFinder's hard 50-result-per-search cap, so you get the full listing set, not just page one.
• 🧹 Cross-quadrant deduplication — the same listing surfacing in overlapping quadrants is written once, keyed by listing ID.
• 🧯 Per-quadrant fault isolation — one bad or empty quadrant is logged and skipped; it never fails the whole run.
• 🏙️ ~100-metro city lookup — pass a city + state and skip hand-drawing a bounding box; power users can still supply exact lat/lng viewports.
• 🧊 Clean, typed dataset rows — Pydantic-validated, ISO-8601 timestamps, stable listing IDs, JSON / CSV / Excel export straight from the Apify Console.
• 💰 Pay-Per-Event pricing — you only pay for results that hit your dataset. No data, no charge.

💡 Use cases

• Travel-nurse and corporate-relocation staffing agencies refreshing available-unit inventory by metro.
• Corporate-housing operators tracking competitor pricing and availability.
• PropTech researchers building a point-in-time dataset of furnished-rental supply.
• Lead generation — surface newly listed units in a target metro on a schedule.

⚙️ How to use it

1. Click Try for free at the top of the page.
2. Fill in the input form — most fields have sensible defaults.
3. Click Start. Output streams into the run's dataset.
4. Export from Storage → Dataset as JSON, CSV, or Excel — or fetch via the API.

📥 Input

Field	Type	Required	Default	Notes
city	string	no	'Austin'	US city to search, e.g. "Austin". Must be paired with State. Matched case-insensitively against a built-in ~100-metro…
state	string	no	'TX'	2-letter USPS state code paired with City, e.g. "TX".
minLatitude	number	no	'—'	Direct viewport override — minimum latitude (-90..90). Required together with Max latitude, Min longitude, and Max…
maxLatitude	number	no	'—'	Direct viewport override — maximum latitude (-90..90). Required together with Min latitude, Min longitude, and Max…
minLongitude	number	no	'—'	Direct viewport override — minimum longitude (-180..180). Required together with Max longitude, Min latitude, and Max…
maxLongitude	number	no	'—'	Direct viewport override — maximum longitude (-180..180). Required together with Min longitude, Min latitude, and Max…
maxResults	integer	no	500	Row cap for this run; also bounds the recursive quadrant-tiling used to get past FurnishedFinder's…
maxPhotosPerListing	integer	no	5	Truncates the photo_urls list per row, even when the source has more photos.
proxyConfiguration	object	no	{'useApifyProxy': True, 'apifyProxyGroups': ['BUYPROXIES94952'], 'apifyProxyCountry': 'US'}	Apify Proxy configuration. Defaults to the BUYPROXIES94952 datacenter group pinned to US — no anti-bot wall was found…

Example input

{
  "city": "Austin",
  "state": "TX",
  "maxResults": 5,
  "maxPhotosPerListing": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "BUYPROXIES94952"
    ],
    "apifyProxyCountry": "US"
  }
}

📤 Output

Every row is one dataset item.

Field	Type	Notes
listing_id	string	FurnishedFinder's own listing identifier, e.g. "1041111_1".
title	string	Listing name/headline.
property_type	string	Property type, e.g. "House", "Apartment", when the source provides it.
bedroom_count	integer	Number of bedrooms.
bathroom_count	number	Number of bathrooms (fractional, e.g. 2.5).
monthly_rent_amount	string	Monthly rent amount as a decimal string, e.g. "3700.00".
currency	string	Currency code for monthly_rent_amount, e.g. "USD".
photo_urls	array	Listing photo URLs, capped at maxPhotosPerListing.
listing_url	string	Best-effort derived link to the listing's detail page — unconfirmed against every listing's real URL shape.
search_city	string	Echo of the resolved search input — "City, ST" or "custom-bbox".
scraped_at	string	ISO-8601 UTC timestamp of when the row was scraped.

Example output

{
  "listing_id": "1041111_1",
  "title": "Spacious 3BR + Office + Bonus Family Room | Brushy Creek",
  "property_type": "House",
  "bedroom_count": 3,
  "bathroom_count": 2.5,
  "monthly_rent_amount": "3700.00",
  "currency": "USD",
  "photo_urls": [
    "https://staticproperties.furnishedfinder.com/1041111/1/1041111_1_69896931-full.jpg"
  ],
  "listing_url": "https://www.furnishedfinder.com/property/1041111",
  "search_city": "Austin, TX",
  "scraped_at": "2026-09-19T00:00:00Z"
}

💰 Pricing

Pay-Per-Event — you pay only when these events fire:

Event	USD	What it is
actor-start	$0.2	One-off warm-up charge per run
result-row	$0.004	Per unique dataset item

Example: 1 000 listings at the rates above ≈ $4.20. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit.

🚧 Limitations

• US listings only — FurnishedFinder does not list outside the US.
• Search-time fields only: full description/amenities and detail-page fields (exact address, host contact, reviews) are out of scope for v1.
• listing_url is a best-effort derived link from the listing ID; it has not been confirmed against every listing's real detail-page URL.
• A single run stops at 500 quadrant queries; an extremely dense bounding box may hit that cap before exhausting Max results.

❓ FAQ

Do I need a FurnishedFinder account or API key?

No. The Actor calls FurnishedFinder's own public search API directly — no login, cookies, or key required.

What if my city isn't in the built-in list?

Use the direct latitude/longitude bounding-box fields instead of City/State — any US map viewport works.

Why did my run return fewer rows than Max results?

FurnishedFinder caps a single search at 50 results; the Actor recursively splits the map into quadrants to go past that, up to a safety cap on total queries per run. A very dense metro may still under-count at the deepest tiling level — see Limitations.

💬 Your feedback

Spotted a bug, hit a weird edge case, or need a new field? Open an issue on the Actor's Issues tab on Apify Console — we ship fixes weekly and we read every report.

---