Homedy Real Estate Scraper: Up to 1,000 Free Results a Month (2026)

Each listing record carries 34 fields when fully enriched, detailing prices, areas, descriptions, and agent contacts directly from homedy.com. This data collection operates without requiring accounts, cookies, or residential proxies, extracting clean properties for search or specific URLs. A thousand results cost $5.00 on the free-plan tier, which also allows you to test the scraper with no initial investment. This tool is built for real estate investors and market analysts who need structured Vietnamese datasets, though teams looking for immediate translation to English should look elsewhere as listings remain in Vietnamese.

Try it before you read further. Apify's free plan includes $5.00 of usage every month with no credit card, enough for up to 1,000 results at $0.005 each before platform usage. Open Homedy Real Estate Scraper on Apify and run the prefilled example.

How reliable is Homedy Real Estate Scraper in production?

Across the last 30 days of public runs on the Apify platform, Homedy Real Estate Scraper recorded 61 runs with the following outcomes.

No run failed or timed out in the last 30 days; the 34 that did not finish were stopped by the people who started them. Keep a retry and an alert on scheduled runs all the same: a clean month is a record, not a guarantee.

What does it cost to run Homedy Real Estate Scraper?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

Worked example: collecting 10,000 results costs $50.00 in result charges before run-start fees and platform usage. No run failed or timed out in the last 30 days, so the list price is a fair budget; keep a retry in place all the same.

The main cost driver is the enrichDetail setting, as it executes an additional request per listing to retrieve secondary fields. To minimize costs, perform your initial search filtering with enrichDetail set to false, and only enable it once you are ready to fetch comprehensive contact and gallery data. Using the maxItems setting ensures you control your exact result charges.

How do you run Homedy Real Estate Scraper from the API?

The schema marks 1 of its 16 controls as required: mode. Nothing in the payload below is illustrative. Those are the schema's prefilled defaults for Homedy Real Estate Scraper, so the request works once your token is in place.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~homedy-real-estate-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search"}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "search"
}

run = client.actor("crawlerbros~homedy-real-estate-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "mode": "search"
}

const run = await client.actor('crawlerbros~homedy-real-estate-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

Because the call is synchronous, your client waits for the whole run. Keep it for exploration. For scheduled work, start the run without waiting and collect the dataset afterwards, so network trouble costs you a retry rather than the results.

Which Homedy Real Estate Scraper inputs matter, and which can you skip?

The mode parameter dictates the entire running style of the Actor and must be specified. Most search runs will rely on category and province to filter properties, while optional parameters like customProvinceSlug and districtSlug should only be configured when targeting highly specific local real estate markets.

• mode (string): What to fetch. Default: "search".
• category (string): Property type + transaction type. Default: "ban-nha-dat".
• province (string): Restrict to one province/city. Leave blank for all of Vietnam. Use Custom province slug to target a province not in this curated list. Default: "ha-noi".
• customProvinceSlug (string): URL slug of any Vietnamese province not in the dropdown, e.g. thua-thien-hue, binh-thuan, an-giang. Takes priority over province when set.
• districtSlug (string): URL slug of a district/ward within the chosen province to narrow results further, e.g. quan-ba-dinh, quan-1, thanh-pho-thu-duc, quan-cau-giay. Has no effect if province/customProvinceSlug is not set (homedy.com has no district-only browse URL).
• listingUrls (array): Full homedy.com listing detail URLs (must end in -es<id>). Default: [].
• projectUrls (array): Full homedy.com project (dự án) URLs (must end in -pj<id>), e.g. https://homedy.com/astral-city-pj76427740. Returns the project's own overview (developer, land area, unit count, sale status) rather than a single unit's listing. Default: [].
• keyword (string): Free-text term submitted to homedy.com's own search box (e.g. vinhomes, chung cư, biệt thự). Re-ranks/biases browse results toward listings whose title or description match the term - a relevance boost like the site's own search, not a strict substring filter, so some results may still not literally contain the term.
• sortBy (string): Client-side sort applied to collected results (homedy.com's own sort UI is JavaScript-only and not reachable via URL, so this actor sorts the fetched page results itself). Default: "".
• minPriceBillionVnd (number): Drop listings cheaper than this, in billion VND (tỷ). E.g. 2 = 2,000,000,000 VND. Listings with no parseable price (e.g. "Thỏa thuận"/negotiable) always pass.
• maxPriceBillionVnd (number): Drop listings more expensive than this, in billion VND (tỷ).
• minAreaM2 (number): Drop listings smaller than this area in square meters.

The other 4 controls, with their defaults, are listed in the input schema on Homedy Real Estate Scraper on Apify.

Fixed-choice controls: mode accepts search (Browse by category + province), byUrl (Fetch listings by URL), project (Fetch project (dự án) overview by URL); category accepts 11 values (default ban-nha-dat), including ban-nha-dat (All property for sale), cho-thue-nha-dat (All property for rent), ban-can-ho-chung-cu (Apartment for sale), cho-thue-can-ho-chung-cu (Apartment for rent); province accepts 16 values (default ha-noi), including ha-noi (Hà Nội), "" (All Vietnam), tp-ho-chi-minh (TP. Hồ Chí Minh), da-nang (Đà Nẵng); sortBy accepts "" (Default (site order)), priceAsc (Price: Low to High), priceDesc (Price: High to Low), areaAsc (Area: Small to Large), areaDesc (Area: Large to Small).

What does Homedy Real Estate Scraper return?

The returned records are ideal for statistical property valuation, agent lead generation, and local price tracking. They do not contain auto-translated English descriptions, nor do they include coordinate-based geofencing if the original poster did not provide an exact address.

listing records (search/byUrl` modes)

• listingId: Numeric homedy.com listing ID
• title: Listing title
• sourceUrl: Canonical listing page URL
• priceText: Display price as shown on site (e.g. "2,6 Tỷ")
• priceVnd: Parsed price in plain VND (omitted for negotiable-price listings)
• areaText: Display area (e.g. "59 m2")
• areaM2: Parsed area in m²
• pricePerM2Text: Display price per m²
• pricePerM2Vnd: Parsed price per m² in VND
• address: Full display address
• province: Province / city name
• district: District name (detail mode / enrichDetail)
• description: Listing description
• imageUrl: Primary listing image
• imageUrls[]: Full image gallery (detail mode / enrichDetail)
• publishedRelative: Relative publish time as shown on site, e.g. "2 ngày trước" (search mode)
• postedDate: Original posting date, ISO yyyy-mm-dd (detail mode / enrichDetail)
• expiryDate: Listing expiry date, ISO yyyy-mm-dd (detail mode / enrichDetail)
• listingType: "sale" or "rent", as declared on the listing itself (detail mode / enrichDetail)
• propertyType: Property type as declared on the listing, e.g. "Căn hộ" (apartment), "Nhà riêng" (private house) (detail mode / enrichDetail)
• houseDirection: House-facing direction, e.g. "Đông-Bắc" (Northeast), when the poster specified one (detail mode / enrichDetail)
• balconyDirection: Balcony-facing direction, when the poster specified one (detail mode / enrichDetail)
• bedroomCount: Number of bedrooms, when the poster specified one (detail mode / enrichDetail)
• floorCount: Number of floors/stories, when the poster specified one (detail mode / enrichDetail)
• isCornerUnit: Whether the unit is a corner unit (true/false), when the poster specified it (detail mode / enrichDetail)
• furnishing: Furnishing level, e.g. "cơ bản" (basic), when the poster specified one (detail mode / enrichDetail)
• amenities[]: In-unit interior/furniture amenities the poster tagged (e.g. "Bình nóng lạnh" water heater, "Tủ bếp" kitchen cabinets, "Giường ngủ" bed), when the listing has an amenities section (detail mode / enrichDetail)
• legalStatus: Legal/title-deed status, when the poster filled it in rather than leaving the site's "--" placeholder (detail mode / enrichDetail)
• posterName: Display name of the agent/owner who posted the listing (detail mode / enrichDetail)
• posterUrl: Link to the poster's public homedy.com profile page (detail mode / enrichDetail)
• posterPhone: The poster's contact phone number (detail mode / enrichDetail)
• posterListingsCount: Total number of active listings posted by that agent/owner (detail mode / enrichDetail)
• recordType: Always "listing"
• scrapedAt: UTC ISO timestamp

project records (project` mode)

• projectId: Numeric homedy.com project ID
• projectName: Project/development name
• sourceUrl: Canonical project page URL
• address: Full display address
• province: Province / city name
• propertyCategory: Property type sold in this project, e.g. "Căn hộ" (apartment)
• priceFromText / priceFromVnd: Starting price, display text and parsed VND
• landAreaText / landAreaM2: Total land area, display text and parsed m²
• constructionAreaText: Total construction/floor area (when published)
• startDate / completionDate: Construction start / handover timeframe (when published)
• buildingCount: Number of buildings/blocks (when published)
• unitCount: Number of units/products (when published)
• unitAreaRangeText: Range of unit sizes offered, e.g. "45;90" (when published)
• status: Sale status, e.g. "Đang mở bán" (now selling)
• developerName / developerUrl: Developer/investor name and homedy.com profile link
• activeListingsCount / activeListingsUrl: Count and link to this project's currently active for-sale/for-rent listings
• amenities[]: On-site amenities the project advertises, e.g. "Bể bơi ngoài trời" (outdoor pool), "Trường mầm non" (kindergarten), "Hệ thống PCCC" (fire-safety system) - grouped categories (facilities, security, education, dining, sports, etc.) flattened into one list
• imageUrl / imageUrls[]: Project cover image / gallery
• recordType: Always "project"
• scrapedAt: UTC ISO timestamp

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open Homedy Real Estate Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

1. Select your target mode based on the desired data structure: choose search for general category scraping, byUrl to scrape specific homedy.com pages, or project to get broad developer and estate overviews.
2. Set the category control to target a specific listing type, such as ban-can-ho-chung-cu for apartments for sale or cho-thue-nha-rieng for private house rentals.
3. Narrow down the geographical scope by selecting from the province dropdown, or input a custom string in customProvinceSlug to capture regions outside of the pre-filled list.
4. Input a specific area like quan-1 or quan-ba-dinh into the districtSlug control to filter localized listings within your chosen province.
5. Toggle the enrichDetail boolean to true if your pipeline requires agent contact numbers (posterPhone) or the full content of the listing descriptions.
6. Set a conservative maxItems value between 10 and 50 to run a dry test run of your selected query parameters.
7. Examine the output dataset to ensure that fields like priceVnd and areaM2 are parsed into numeric formats before scaling up your dataset collection.

How do you apply it? Three worked playbooks

These are Homedy Real Estate Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Real estate investors

Outcome: Screen apartments/houses/land by price and area range across a province

Configure: Set mode to "search", category to "ban-can-ho-chung-cu", province to "ha-noi", minPriceBillionVnd to 2, maxPriceBillionVnd to 5, and maxItems to 100.

Working method: Execute a dry run for your chosen province to check the average pricing density, then refine the boundaries of minPriceBillionVnd and maxPriceBillionVnd to match your investment strategy. Verify that the parsed areaM2 fields align with your targeted layout size before exporting the final dataset.

Deliverable: A spreadsheet containing structured listings with parsed prices in VND, areas in square meters, and direct links to the property pages.

Stop condition: The runner begins emitting records with missing or null priceVnd values for listings that clearly exhibit structured price text.

Use case 2: Rental market tracking

Outcome: Monitor rental price trends in a specific district over time

Configure: Set mode to "search", category to "cho-thue-nha-rieng", province to "tp-ho-chi-minh", districtSlug to "quan-1", and maxItems to 200.

Working method: Schedule the scraper to run on a weekly interval using the designated districtSlug. Compare successive datasets by indexing listingId to isolate newly published rentals, rent hikes, or properties that have been taken off the market.

Deliverable: A localized dataset tracking rental trends, listing activity, and price-per-square-meter changes over consecutive runs.

Stop condition: The dataset contains empty district fields, indicating a mismatch between the districtSlug and the parent province.

Use case 3: Lead generation

Outcome: Collect poster (agent) contact info for outreach via enrichDetail

Configure: Set mode to "search", category to "ban-nha-dat", province to "binh-duong", enrichDetail to true, and maxItems to 150.

Working method: Trigger the scraper with enrichDetail activated to ensure the sub-requests pull contact details. Extract posterName, posterUrl, and posterPhone from each listing record, grouping the results by agent to clean up duplicate contact numbers.

Deliverable: A clean contact directory of active property agents and private landlords containing names, profile links, and direct telephone numbers.

Stop condition: The posterPhone field returns empty across ten consecutive enriched listing records.

What breaks, and how do you design around it?

• homedy.com's sort dropdown is rendered entirely client-side (no working server-side sort query parameter was found after live testing) - sortBy is therefore applied locally to the fetched results rather than passed upstream.
• keyword is submitted as homedy.com's own ?keyword= query parameter (verified live: deterministic, same term always returns the same result set). It behaves as a relevance boost rather than a strict substring filter - some returned listings may not literally contain the term in their title/description, matching the site's own search-box behavior.
• province ships a curated list of 15 major provinces/cities; use customProvinceSlug for the remaining Vietnamese provinces (URL-slug form, e.g. thua-thien-hue, an-giang).
• bedroomCount, legalStatus, balconyDirection, floorCount, isCornerUnit, and furnishing come from each listing's structured "product attributes" block on the detail page (enrichDetail mode) - they're only emitted when the poster actually filled them in; homedy.com's own "--" placeholder for unset attributes is treated as empty and omitted rather than passed through literally. Bathroom count was not found as a structured attribute on any sampled listing and is therefore not included.

When targeting a province not listed in the standard dropdown, look up the URL slug on homedy.com and input it into customProvinceSlug. If the client-side sortBy does not align with your system's sorting logic, ingest the raw data first and apply post-processing sorting inside your own database.

When should you not use Homedy Real Estate Scraper?

Do not use this scraper if your target real estate market is located outside of Vietnam, as homedy.com only publishes properties within Vietnamese territory. For other European or regional markets, you should use specialized regional extractors. For instance, if you are looking to aggregate listings in Western Europe, the Immoweb Belgian Real Estate Scraper or SeLoger French Real Estate Scraper are much better fits. If your research is focused on Southeast Asian markets outside of Vietnam, utilize the Lamudi Real Estate Scraper which is dedicated to Philippine property data.

What should you check before trusting the output?

• Verify that the priceVnd field is present for non-negotiable listings, and flag any records where the raw priceText contains numeric values but priceVnd is null.
• Check that posterPhone contains a valid Vietnamese phone number string when enrichDetail is enabled, and trigger an alert if contact fields are uniformly empty across multiple records.
• Monitor the ratio of project records to listing records, ensuring that mode is set to project when scraping -pj URLs so that developerName and unitCount populate correctly.
• Audit the geographical output by checking that the province field matches your customProvinceSlug input when targeting niche cities outside the main dropdown.
• Assess the percentage of listings returning empty descriptions or truncated titles, which typically points to a change in the site's layout markup.

None of this proves a record is correct. It gives a scheduled Homedy Real Estate Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

What is the expected success rate of the Homedy scraper?

Out of 61 runs in the last 30 days, 27 succeeded, with 0 failing and 34 being aborted by users. This indicates that the Actor has a 100% system success rate when excluding user-terminated runs, meaning it does not experience regular runtime crashes or timeouts.

Do I need to pay for proxies to use this scraper?

No. The scraper accesses homedy.com's public pages directly from Apify's datacenters. It automatically routes through Apify's proxy network only when it encounters a 403 or 429 status code, meaning you do not need to purchase expensive residential proxies to run it.

How are negotiable prices handled in the output?

When a listing has a negotiable price (indicated as "Thỏa thuận"), the priceVnd field is omitted from the dataset. This design decision ensures you do not receive arbitrary placeholder values like 0 or null, allowing you to easily filter out negotiable items.

Can I search for properties in smaller provinces not listed in the dropdown?

Yes. You can use the customProvinceSlug control to input the exact URL slug of any Vietnamese province. This overrides the curated province selection list, enabling complete coverage of smaller municipalities across Vietnam.

How much does it cost to scrape 5,000 listings with full details?

On the free-plan price tier, 1,000 results cost $5.00, making 5,000 results cost $25.00 in result fees. Keep in mind that Apify also charges platform usage fees for each run on top of the result costs, and using enrichDetail increases the execution time.

Where to go next

When you are ready to run it, open Homedy Real Estate Scraper on Apify; the free plan covers up to 1,000 results a month.

Start with the Homedy Real Estate Scraper Actor page for the current input schema, pricing tier, and run history.

It is part of the Real Estate Scrapers, which puts every related Actor on one page with its price and run history.

Other Actors we maintain for related data:

• Immoweb Belgian Real Estate Scraper: Scrape property listings from Immoweb.be (houses, apartments, land for sale or rent in Belgium) with price, bedrooms, bathrooms, living area, postcode, locality, energy class, images and more.
• Lamudi Real Estate Scraper: Scrape real estate listings from lamudi.com.ph - condos, houses, apartments, land and commercial property for sale or rent across the Philippines.
• Zameen Real Estate Scraper: Scrape Pakistani real estate listings from zameen.com - houses, plots, and commercial property for sale or rent.
• SeLoger French Real Estate Scraper: Scrape SeLoger.com property listings (apartments, houses, sale & rent) in France with title, price, surface, rooms, address, GPS, energy class, images, agency.
• ZonaProp Scraper: Scrape real estate listings from ZonaProp.com.ar, Argentina's leading property portal.
• Imovirtual Real Estate Scraper: Scrape property listings from Imovirtual.com - Portugal's #1 real estate portal.
• StreetEasy Scraper: Scrape NYC real estate listings from StreetEasy including sales and rentals with prices, addresses, amenities, agent info, and more.
• Idealista Scraper: Scrape real estate listings from Idealista.com.

Related guides:

• Crexi Real Estate Scraper: 18 Data Fields per Record (2026)
• Redfin Real Estate Scraper: Up to 2,500 Free Results a Month (2026)
• United Real Estate Homes for Sale Scraper: 3 Practical Use Cases
• ZonaProp Scraper: Operating Playbooks and Workflows

Resources

• Actor documentation, input schema, and pricing: verified against the published Actor on 2026-10-06.

• Actor last updated by its maintainers on 2026-08-03.

• Run outcome figures cover the 30 day public window ending 2026-10-06.

• Homedy Real Estate Scraper on Apify