Homedy Real Estate Scraper
Pricing
from $3.00 / 1,000 results
Homedy Real Estate Scraper
Scrape homedy.com - a leading Vietnam real estate marketplace. Browse by category (apartment, house, land, office, ...) and province, or fetch full listing detail by URL. Prices, area, description, images.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
Crawler Bros
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Scrape homedy.com — a leading Vietnam real estate marketplace. Browse listings by category (apartment, house, land, office, ...) and province, or fetch full detail for specific listing URLs. No login, no cookies, no residential proxy required.
What this actor does
- Three modes:
search(browse by category + province, with sort and price/area filters),byUrl(fetch specific listings directly), andproject(fetch a development's own overview — developer, land area, unit count, sale status, on-site amenities — by project URL) - 11 property/transaction categories: apartments, houses, villas, land, offices — for sale or for rent
- Vietnamese price/area parsing:
"2,6 Tỷ"and"59 m2"are parsed into plain numeric VND and m² fields alongside the original display text - Optional detail enrichment: full description, district, complete image gallery, posted/expiry dates, listing type (sale/rent), property type, house direction, and poster (agent) contact info
- Empty fields are omitted — every record only contains fields that were actually extracted
Modes
Search (mode: "search")
Browse listings by category (property + transaction type) and province. Supports client-side sortBy (price/area ascending or descending — homedy.com's own sort control is JavaScript-only and not reachable via a URL parameter, so this actor fetches the category pages and sorts the collected results itself) plus minPriceBillionVnd/maxPriceBillionVnd and minAreaM2/maxAreaM2 filters.
By URL (mode: "byUrl")
Fetch one or more specific listing detail pages directly by URL (listingUrls) — always returns the full enriched record (full description, all images, district, posted/expiry dates, listing type).
Project (mode: "project")
Fetch one or more homedy.com project (dự án) overview pages directly by URL (projectUrls) — a project page describes an entire development (developer, land area, unit count, sale status, active-listings count), not one for-sale/for-rent unit. Project URLs end in -pj<id>, e.g. https://homedy.com/astral-city-pj76427740.
Output fields
listing records (search / byUrl modes)
| Field | Description |
|---|---|
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)
| Field | Description |
|---|---|
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 |
Fields marked "when published" are frequently shown as "Đang cập nhật" (updating) on homedy.com itself — the actor omits those rather than emitting a placeholder string.
Input
| Field | Type | Default | Description |
|---|---|---|---|
mode | string | search | search / byUrl / project |
category | string | ban-nha-dat | 11 curated property + transaction type combinations (mode=search) |
province | string | ha-noi | 15 curated major provinces/cities, or blank for all Vietnam (mode=search) |
customProvinceSlug | string | – | URL slug of any Vietnamese province not in the dropdown, overrides province (mode=search) |
districtSlug | string | – | Narrow to one district/ward within the chosen province, e.g. quan-ba-dinh, quan-1 (mode=search, requires province/customProvinceSlug) |
keyword | string | – | Free-text term submitted to homedy.com's own search box — a relevance boost, not a strict substring filter (mode=search) |
sortBy | string | site order | Price/area ascending or descending, applied client-side (mode=search) |
minPriceBillionVnd / maxPriceBillionVnd | number | – | Price range in billion VND (tỷ). For sale listings typical values are 1-50+. For rental categories (cho-thue-*), prices are monthly rent in millions VND — use small fractional values (e.g. 0.01 = 10 million VND/month) |
minAreaM2 / maxAreaM2 | number | – | Area range in m² |
listingUrls | array | [] | Full homedy.com listing detail URLs, must end in -es<id> (mode=byUrl) |
projectUrls | array | [] | Full homedy.com project URLs, must end in -pj<id> (mode=project) |
enrichDetail | boolean | false | Fetch each listing's detail page for full description, district, image gallery (mode=search) |
maxItems | integer | 30 | Hard cap on emitted records (1-500) |
proxyConfiguration | object | Apify Proxy (auto) | homedy.com is reachable directly; proxy only engages automatically on a 403/429 |
Example: browse apartments for sale in Hanoi
{"mode": "search","category": "ban-can-ho-chung-cu","province": "ha-noi","minPriceBillionVnd": 2,"maxPriceBillionVnd": 5}
Example: browse rentals in a specific district with full detail
{"mode": "search","category": "cho-thue-nha-rieng","province": "tp-ho-chi-minh","districtSlug": "quan-1","enrichDetail": true}
Example: fetch specific listings by URL
{"mode": "byUrl","listingUrls": ["https://homedy.com/ban-can-ho-chung-cu-vinhomes-es12345678"]}
Example: fetch a project overview
{"mode": "project","projectUrls": ["https://homedy.com/astral-city-pj76427740"]}
Use cases
- Real estate investors — screen apartments/houses/land by price and area range across a province
- Market research — build a comparison dataset of listings by category and location
- Rental market tracking — monitor rental price trends in a specific district over time
- Developer/project research — pull a development's unit count, sale status, and amenities from its project page
- Lead generation — collect poster (agent) contact info for outreach via
enrichDetail
Limitations
- homedy.com's sort dropdown is rendered entirely client-side (no working server-side sort query parameter was found after live testing) —
sortByis therefore applied locally to the fetched results rather than passed upstream. keywordis 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.provinceships a curated list of 15 major provinces/cities; usecustomProvinceSlugfor the remaining Vietnamese provinces (URL-slug form, e.g.thua-thien-hue,an-giang).bedroomCount,legalStatus,balconyDirection,floorCount,isCornerUnit, andfurnishingcome from each listing's structured "product attributes" block on the detail page (enrichDetailmode) — 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.
FAQ
Is this affiliated with homedy.com? No, this is a third-party actor built against homedy.com's public pages; it is not affiliated with or endorsed by homedy.com.
Do I need a proxy or login? No — every request runs against homedy.com's public, unauthenticated pages directly. A proxy input is exposed and automatically engaged as a fallback only if a run is ever blocked (403/429), but it isn't required in normal operation.
Why is priceVnd sometimes missing? Some listings display "Thỏa thuận" (negotiable/by agreement) instead of a price — that's real data, not a parsing failure, so no price field is emitted rather than a fake 0 or null.
What's the difference between search fields and enrichDetail fields? The browse/category page already contains price, area, price/m², address, description, image, and publish time. Turning on enrichDetail adds one extra request per listing to also capture the full description, complete image gallery, and district — useful for smaller batches where completeness matters more than speed.
How current is the data? Real-time — every run fetches homedy.com's live pages directly.
Can I search a province that isn't in the dropdown? Yes — set customProvinceSlug to the URL slug of any Vietnamese province (e.g. thua-thien-hue); it overrides province when set.