REAL ESTATE · PERU
Urbania Peru Property Listings
Property listings for rent and sale from Urbania.pe, Peru's largest real-estate portal.
About this data
Property listings for rent and sale from Urbania.pe, Peru's largest real-estate portal. Keyword search, optional detail enrichment (full description, posting date, seller contact, gallery), structured fields: price, currency, rooms, bathrooms, area, address, publisher. 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
One endpoint 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.
POST /v1/pe/urbania/listings
Live property listings from Urbania, Peru's leading real-estate portal, for a city slug (lima by default, e.g. arequipa) and optional keyword, for sale or rent: price and currency (PEN or USD), area in m2, rooms, bathrooms where shown, address, publisher, image and listing URL.
First results page only, no detail pages, up to 20 listings per call; the residential proxy is included in the price.
Input
Send a JSON body to POST https://api.ssh.autos/v1/pe/urbania/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
operation | string | optional | one of sale, rentals; default "sale" |
city | string | optional | up to 60 characters; pattern ^[a-z0-9]+(-[a-z0-9]+)*$; default "lima" |
search | string | optional | 2–80 characters |
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 20 fields; a field the source does not publish comes back null.
20 fields per record
| Field | Type | Notes |
|---|---|---|
id | string | Numeric listing id from the URL tail; not guaranteed unique when datasets are merged, prefer listingKey. |
listingKey | string | Composite unique key: source:id (e.g. urbania.pe:148218236). |
url | string | Canonical Urbania listing URL (tracking query parameters removed). |
name | string | Listing/publisher display name from the ld+json block. |
priceAmount | number | Advertised price amount from the listing card; null when the card says 'Consultar precio'. |
priceCurrency | string | PEN or USD; first currency shown when the card lists both. |
operation | string | Requested operation: 'rentals' or 'sale'. |
city | string | Requested city slug, e.g. 'lima'. |
source_query | string | Keyword term applied via the ?keyword= URL filter (input 'search'); null on non-search runs. |
address | string | Location line from the card (district, city) or the ld+json postal address. |
rooms | integer | Bedrooms (dormitorios) parsed from card features; upper bound for ranges. |
bathrooms | integer | Bathrooms parsed from card features. |
areaM2 | number | Total area in m² parsed from card features; upper bound for ranges. |
publisher | string | Publisher/broker name from the ld+json listing block. |
imageUrl | string | Primary listing image URL (CDN). |
postedAt | string | Exact publication timestamp from the detail page as ISO-8601 (includeDetails; null on card-only runs). |
sellerContact | string | Public seller email/phone plainly rendered on the detail page (includeDetails; Urbania usually hides these behind a 'Ver teléfono' action, so commonly null). |
additionalImageUrls | array of strings | Gallery image URLs from the detail page, capped at 10 (includeDetails). |
source | string | Source website hostname. |
collectedAt | string | UTC ISO-8601 collection timestamp. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/pe/urbania/listings -m POST -b '{"operation": "rentals", "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.
- 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.
- 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: Urbania Peru Property Listings Scraper. 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