Lamudi.ph Property Scraper avatar

Lamudi.ph Property Scraper

Pricing

from $0.95 / 1,000 results

Go to Apify Store
Lamudi.ph Property Scraper

Lamudi.ph Property Scraper

Extract real estate listings from Lamudi.ph instantly. Scrape property prices, locations, agent details & descriptions for the Philippine market analysis. Perfect for property investors, market researchers & lead generation. Automate your real estate data collection efficiently.

Pricing

from $0.95 / 1,000 results

Rating

5.0

(4)

Developer

Shahid Irfan

Shahid Irfan

Maintained by Community

Actor stats

3

Bookmarked

35

Total users

4

Monthly active users

7 days ago

Last modified

Share

What does Lamudi Philippines Property Scraper do?

Lamudi Philippines Property Scraper collects structured property listings from public Lamudi Philippines catalog pages. Give it one Lamudi search or catalog URL, such as a house-for-sale page, and it returns listing titles, prices, property attributes, locations, images, descriptions, agency information, tags, and source URLs in an Apify dataset.

Use the dataset for Philippine real estate market research, property inventory monitoring, price analysis, listing research, and lead preparation. The Actor can collect sale or rental categories when the supplied Lamudi URL points to that catalog.

Why use Lamudi Philippines Property Scraper?

  • Structured property records - Turn Lamudi listing pages into records that are easier to filter, compare, and store.
  • Useful real estate fields - Collect prices, bedrooms, bathrooms, area, location, coordinates, media links, descriptions, and agency data when Lamudi publishes them.
  • Controlled collection size - Use results_wanted to set the target number of records and max_pages to limit page coverage.
  • Cleaner datasets - Duplicate listing IDs are removed during a run, and empty values are omitted from saved records.
  • Workflow-ready exports - Review the dataset in Apify, download it in common formats, or connect it to downstream tools through Apify integrations.

What data can you extract from Lamudi Philippines?

The Actor saves one dataset item per unique listing ID. The fields below are available when the source provides the corresponding information.

FieldTypeDescription
idStringLamudi listing identifier used for deduplication.
titleStringProperty listing title.
urlStringDirect Lamudi property URL.
purposeStringPurpose inferred from the first path segment, such as buy or rent.
categoryStringCategory inferred from the catalog URL path, such as house or condo.
priceNumberNumeric listing price after removing currency symbols and separators.
priceTextStringOriginal formatted price text, such as ₱ 6,113,580.
bedroomsNumberNumber of bedrooms when available.
bathroomsNumberNumber of bathrooms when available.
areaNumberNumeric area value parsed from the source value.
areaTextStringOriginal area text, such as 80 sqm.
carSpacesNumberNumber of car spaces when published.
locationStringListing location text.
latitudeNumberLatitude when published by Lamudi.
longitudeNumberLongitude when published by Lamudi.
exactLocationBooleanSource flag indicating whether the listing has an exact location.
photoCountNumberNumber of listing images reported by the source.
coverPhotoUrlStringPrimary listing image URL when available.
imageUrlStringPrimary listing image URL, matching coverPhotoUrl when saved.
imageUrlsArrayAn array containing the available primary image URL. This is not a full gallery.
descriptionStringListing description text.
agentNameStringAgency display name from the source agency data when available.
agencyDataObjectAgency metadata published with the listing.
tagsObjectSource tag metadata for the listing.
tagLabelsArrayHuman-readable tag text extracted from tags.
_sourceUrlStringLamudi catalog URL used for the collection.

How to scrape Lamudi Philippines property listings

  1. Open a public Lamudi Philippines catalog or search page.
  2. Copy the URL into the Actor's startUrl field.
  3. Set results_wanted and max_pages for the collection size you need.
  4. Keep the default Apify Proxy configuration for larger or repeated runs, or provide your own supported proxy configuration.
  5. Start the run and review the dataset preview.
  6. Download the records or connect the dataset to your workflow.

Supported input methods

  • Apify Console form - Enter the catalog URL and numeric limits in the input form.
  • JSON run input - Pass the same fields as a JSON object when starting the Actor programmatically or through an Apify-compatible workflow.
  • One catalog URL per run - The Actor accepts one startUrl. Location, property type, sale or rent mode, and other Lamudi filters must already be represented by that URL.

Input Parameters

ParameterTypeRequiredDefaultDescription
startUrlStringYeshttps://www.lamudi.com.ph/buy/house/Public Lamudi Philippines catalog or search URL to collect.
results_wantedIntegerNo20Target maximum number of unique property listings to save. Minimum is 1.
max_pagesIntegerNo3Maximum number of numbered catalog pages to process. Minimum is 1.
proxyConfigurationObjectNoApify Proxy with RESIDENTIAL groupApify Proxy settings used for the run.

The schema does not provide separate keyword, location, price, bedroom, or property-type fields. To target a filtered result set, provide the corresponding public Lamudi catalog URL in startUrl.

Usage Examples

Basic house listing extraction

Collect up to 20 house listings from the default Lamudi Philippines house catalog.

{
"startUrl": "https://www.lamudi.com.ph/buy/house/",
"results_wanted": 20,
"max_pages": 3
}

Larger collection from a Lamudi category URL

Use a Lamudi category URL and increase the result and page limits for broader market research.

{
"startUrl": "https://www.lamudi.com.ph/buy/condo/",
"results_wanted": 50,
"max_pages": 5
}

Collection with an explicit proxy configuration

Keep proxy access enabled for a larger or recurring run and specify the residential proxy group in the input.

{
"startUrl": "https://www.lamudi.com.ph/buy/house/",
"results_wanted": 100,
"max_pages": 10,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"]
}
}

Sample Output

This example shows one representative dataset item. Optional fields can be absent when the listing does not publish them or when only fallback listing information is available.

{
"id": "41032-73-2a2482086164-9eaa-1976469-a5d0-7c06",
"title": "4BR 2-Storey House and Lot for Sale in Calamba, Laguna",
"url": "https://www.lamudi.com.ph/property/41032-73-2a2482086164-9eaa-1976469-a5d0-7c06",
"purpose": "buy",
"category": "house",
"price": 6113580,
"priceText": "₱ 6,113,580",
"bedrooms": 4,
"bathrooms": 2,
"area": 80,
"areaText": "80 sqm",
"location": "Calamba, Laguna",
"longitude": 121.11005665,
"latitude": 14.18853589,
"exactLocation": true,
"photoCount": 21,
"coverPhotoUrl": "https://img.lamudi.com/example-cover-image.jpg",
"imageUrl": "https://img.lamudi.com/example-cover-image.jpg",
"imageUrls": ["https://img.lamudi.com/example-cover-image.jpg"],
"description": "House listing description published by Lamudi.",
"agentName": "Suntrust Properties, Inc.",
"agencyData": {
"agencyName": "Suntrust Properties, Inc.",
"isPremium": false
},
"tags": {
"verified": {
"text": "Fully verified"
}
},
"tagLabels": ["Fully verified"],
"_sourceUrl": "https://www.lamudi.com.ph/buy/house/"
}

Data quality behavior and limitations

  • The Actor removes repeated records with the same id during a run.
  • Empty strings, empty arrays, empty objects, and null-like values are omitted from the final record.
  • Price and area fields are normalized into numeric values when the source text contains a usable number. Keep priceText and areaText when you need the original display format.
  • imageUrl and imageUrls represent the available primary image, not a complete photo gallery. Image fields are omitted when a usable source image URL is not available.
  • The first catalog page can provide richer listing records. Later pages may be retained with the information visible on the catalog page if optional listing details cannot be retrieved.
  • A run can return fewer records than results_wanted when the catalog has fewer available listings, pages contain no new IDs, or source data is unavailable.
  • Collection stops when it reaches results_wanted, reaches max_pages, or encounters repeated pages without new listings.
  • purpose and category are inferred from the URL path. URLs with additional location segments may produce a category value based on the first two path segments rather than a normalized Lamudi property type.
  • The Actor is for Lamudi Philippines URLs. It does not accept keyword searches, a list of start URLs, or a separate input field for property filters.
  • Public listing pages can change, expire, or omit fields. Review the dataset preview before relying on a field for a production workflow.

Tips for best results

  • Start with the exact filtered URL - Apply the city, property type, sale or rent mode, and other filters on Lamudi first, then copy the resulting public catalog URL.
  • Test a small run - Begin with results_wanted: 20 and a low max_pages value so you can confirm the target catalog and output shape.
  • Use enough pages for the target count - A high results_wanted value cannot be reached if max_pages is too low or the source catalog has limited results.
  • Keep source text fields - Use priceText and areaText alongside normalized numeric fields when preserving the displayed Lamudi values matters.
  • Expect optional fields - Coordinates, car spaces, exact-location status, agency metadata, tags, descriptions, and images depend on what each listing publishes.
  • Review scheduled snapshots - For recurring monitoring, compare records by id and keep the _sourceUrl with each dataset export.

Integrations and export formats

Apify stores the results in a dataset that can be reviewed or connected to other workflows.

  • Apify API - Read dataset items programmatically for dashboards, analysis, or internal applications.
  • Google Sheets - Review prices, locations, and property attributes in a spreadsheet.
  • Airtable - Maintain a searchable property inventory with custom views and fields.
  • Make or Zapier - Send completed dataset results into no-code workflows.
  • Webhooks - Trigger downstream processing after a run completes.
  • JSON - Use for applications and data pipelines.
  • CSV or Excel - Use for spreadsheet analysis and reporting.
  • XML - Use when a downstream system requires XML data.

Frequently Asked Questions

Can I collect houses, condos, apartments, land, and commercial properties?

Yes, when Lamudi provides a public catalog URL for the category. Put that URL in startUrl; the Actor does not use separate category input fields.

Can I collect both sale and rental listings?

Yes. Use a public Lamudi Philippines catalog URL for the required purpose, such as a sale or rent page. The purpose value is inferred from the URL path.

Can I provide multiple URLs in one run?

No. The current input schema accepts one startUrl per run. Run the Actor separately for additional catalog URLs.

Why did the run return fewer listings than requested?

The source may have fewer available listings, the page limit may be too low, or later pages may contain no new listing IDs. The Actor also stops after repeated pages without new records.

Why is a field missing from a record?

Lamudi does not publish every field for every listing, and missing values are omitted from the record. Detail information may also be unavailable for an individual listing, in which case the available catalog information can be retained.

No. The current output stores the available primary image in coverPhotoUrl, imageUrl, and the single-item imageUrls array. photoCount is the source-reported image count, not the number of URLs returned in imageUrls.

Can I schedule recurring Lamudi collections?

Yes. Apify schedules can start recurring runs so you can compare dataset snapshots over time. The source may change between runs, so review results for missing or changed listings.

You are responsible for complying with Lamudi's terms, applicable privacy rules, and local laws. Use public listing data for legitimate purposes and handle agency or contact-related information responsibly.

Support

For issues, missing fields, source changes, or feature requests, use the Issues tab on the Actor page or contact the developer through Apify.

This Actor is intended for legitimate collection of publicly available Lamudi Philippines property information. Users are responsible for complying with Lamudi's terms of service, applicable laws, privacy requirements, and any restrictions that apply to the data they collect, store, or share.