REAL ESTATE · MEXICO, PHILIPPINES
Lamudi Real-Estate (MX/PH)
Real-estate listings from Lamudi across Mexico and the Philippines.
About this data
Real-estate listings from Lamudi across Mexico and the Philippines. Sale and rental properties with price, currency, property type, area, rooms, location, images and listing URL. On-demand scrape — fresh listings every run.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
2 endpoints at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
Lamudi Mexico new developments for sale, up to 20 per call
POST /v1/mx/lamudi/listings
Live Lamudi Mexico new development listings by property type: development name, property type, city, images and listing URL, plus price and currency, area in m2, bedrooms and bathrooms where shown.
Those numeric fields can be absent from most results.
First results page only, no detail pages, up to 20 listings per call; the proxy is included in the price.
Input
Send a JSON body to POST https://api.ssh.autos/v1/mx/lamudi/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
operation | string | optional | default "buy" |
propertyType | string | optional | one of apartments, houses, land, offices, commercial; default "apartments" |
maxResults | integer | optional | 1–20; default 10 |
Returned fields
The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 19 fields; a field the source does not publish comes back null.
19 fields per record
| Field | Type | Notes |
|---|---|---|
id | string | Numeric listing id from the detail URL, or null when the URL carries no id. |
listing_key | string | Stable record key 'source:id' (e.g. lamudi.com.mx:1234567), or the canonical URL when the listing id is unknown. |
url | string | Canonical listing URL on the portal, tracking query parameters removed. |
name | string | Listing title (JSON-LD name or the card heading); null when not shown. |
price | integer | Advertised price as an integer amount in the local currency ('$4,500,000' -> 4500000). Null when the price is hidden. |
currency | string | Local currency: MXN on lamudi.com.mx, PHP on lamudi.com.ph; null when no price was parsed. |
area_m2 | number | Floor area in m² from the JSON-LD floorSize or the card ('120 m²'); null when not shown. |
bedrooms | integer | Bedroom count from the JSON-LD number of bedrooms or the card ('3 recámaras' / '3 Bedrooms'); null when not shown. |
bathrooms | integer | Bathroom count from the card ('2 baños' / '2 Bathrooms'); null when not shown. |
property_type | string | Requested property type facet (apartments, houses, land, offices, commercial). |
city | string | Listing city: the JSON-LD address locality or the card's location element (address block / breadcrumb) when present, else the listing URL slug's place tail, else the searched city; null when none res… |
images | array of strings | Listing image URLs, deduplicated. |
image_url | string | Primary listing image URL (first entry of images); null when the listing carries no image. |
operation | string | Requested operation: 'buy' or 'rent'. |
location | string | Resolved search location (the portal default when none was requested). |
portal | string | Published record/portal slug the record came from ('lamudi-mx' or 'lamudi-ph'). |
country | string | Portal country: MX or PH. |
source | string | Source website hostname (lamudi.com.mx or lamudi.com.ph). |
collected_at | string | UTC ISO-8601 collection timestamp. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/mx/lamudi/listings -m POST -b '{"maxResults": 3}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
Lamudi Philippines properties for sale or rent, up to 20 per call
POST /v1/ph/lamudi/listings
Live Lamudi Philippines property listings for sale or rent, optionally by location slug: name, price and currency, area in m2, bedrooms, bathrooms, property type, city, images and listing URL.
First results page only, no detail pages, up to 20 listings per call; the proxy is included in the price.
Input
Send a JSON body to POST https://api.ssh.autos/v1/ph/lamudi/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
operation | string | optional | one of buy, rent; default "buy" |
propertyType | string | optional | one of apartments, houses, land, offices, commercial; default "apartments" |
maxResults | integer | optional | 1–20; default 10 |
location | string | optional | up to 80 characters; pattern ^([a-z0-9]+(-[a-z0-9]+)*)?$ |
Returned fields
The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 19 fields; a field the source does not publish comes back null.
19 fields per record
| Field | Type | Notes |
|---|---|---|
id | string | Numeric listing id from the detail URL, or null when the URL carries no id. |
listing_key | string | Stable record key 'source:id' (e.g. lamudi.com.mx:1234567), or the canonical URL when the listing id is unknown. |
url | string | Canonical listing URL on the portal, tracking query parameters removed. |
name | string | Listing title (JSON-LD name or the card heading); null when not shown. |
price | integer | Advertised price as an integer amount in the local currency ('$4,500,000' -> 4500000). Null when the price is hidden. |
currency | string | Local currency: MXN on lamudi.com.mx, PHP on lamudi.com.ph; null when no price was parsed. |
area_m2 | number | Floor area in m² from the JSON-LD floorSize or the card ('120 m²'); null when not shown. |
bedrooms | integer | Bedroom count from the JSON-LD number of bedrooms or the card ('3 recámaras' / '3 Bedrooms'); null when not shown. |
bathrooms | integer | Bathroom count from the card ('2 baños' / '2 Bathrooms'); null when not shown. |
property_type | string | Requested property type facet (apartments, houses, land, offices, commercial). |
city | string | Listing city: the JSON-LD address locality or the card's location element (address block / breadcrumb) when present, else the listing URL slug's place tail, else the searched city; null when none res… |
images | array of strings | Listing image URLs, deduplicated. |
image_url | string | Primary listing image URL (first entry of images); null when the listing carries no image. |
operation | string | Requested operation: 'buy' or 'rent'. |
location | string | Resolved search location (the portal default when none was requested). |
portal | string | Published record/portal slug the record came from ('lamudi-mx' or 'lamudi-ph'). |
country | string | Portal country: MX or PH. |
source | string | Source website hostname (lamudi.com.mx or lamudi.com.ph). |
collected_at | string | UTC ISO-8601 collection timestamp. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/ph/lamudi/listings -m POST -b '{"maxResults": 3}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Lamudi Mexico new developments for sale, up to 20 per call: Confirmed no matches returns records: [] (charged: it is an answer).
- Lamudi Philippines properties for sale or rent, up to 20 per call: Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Lamudi Mexico new developments for sale, up to 20 per call: Invalid input and source failures are not charged.
- Lamudi Philippines properties for sale or rent, up to 20 per call: Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Lamudi Real-Estate Scraper (MX/PH). Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt