Fincaraiz CO Property Scraper (Colombia, Next.js native extraction)

Property listings from fincaraiz.com.co (Colombia): apartment/house searches for sale (venta) and rental (arriendo), scoped by city, normalized to the Navent-family record shape (price COP, area m², bedrooms, bathrooms, address/location, listing URL, images, posted date).

Next.js native extraction — the search page is Next.js SSR, and the complete result set rides a single __NEXT_DATA__ JSON blob embedded in the page. The Actor parses that structured state directly: no browser, no HTML scraping of cards, no OAuth, no challenge solving. A JSON-LD fallback lane covers pages where the state is incomplete.

Access lane (verified 2026-09-04)

www.fincaraiz.com.co 403s plain datacenter egress — IP reputation, not bot protection. The identical request over Colombian residential egress returns the full page (200, ~900 KB). This is exactly the rot that keeps the incumbent mid-tier actor at a ~65% success rate while its README claims "no bot protection requiring proxy": there is no challenge to solve, but the site rejects datacenter IPs, so a proxy-less datacenter lane fails. This Actor makes the residential requirement explicit and verified:

1. External residential proxy (default for portability): pass proxyUrl (optionally proxyUsername/proxyPassword). For DataImpulse, a username without a country suffix automatically gains __cr.co (Colombian exits).
2. Apify platform proxy: with no proxy input the Actor requests the RESIDENTIAL proxy group pinned to CO.
3. A 403 fails fast with a clear error naming the lane requirement — never a silent partial dataset.

Input

Field	Default	Notes
operation	venta	venta (sale) or arriendo (rental). Rent grammar is /arriendo/apartamentos.
propertyType	apartamento	apartamento or casa.
location	(empty)	Optional city or city/department slug — bogota, medellin/antioquia. Free text is slugified (accents fold).
maxPages	1	1–5 pages; 21 postings per page.
maxResults	50	Hard stop, 1–200.
requestDelaySecs	1.0	Delay between page fetches (0.5–10).
proxyUrl	(empty)	CO-residential proxy (see above).

Output

One record per listing (validated against the Actor's dataset schema):

id, listingKey (fincaraiz.com.co:<id>), url, name, price, currency (COP / USD), priceUsd (site-computed), propertyType, areaM2 (built → terrain → m² fallback chain), rooms, bedrooms, bathrooms, parkings, address, location, city, region, latitude, longitude, operation, publisher, postedAt, images[], imageUrl, source, country, scrapedAt.

Usage examples

{ "operation": "venta", "propertyType": "apartamento", "maxResults": 21 }

{
  "operation": "arriendo",
  "propertyType": "casa",
  "location": "medellin/antioquia",
  "maxPages": 2,
  "proxyUrl": "http://user:pass@gw.dataimpulse.com:823"
}

Cost

One page ≈ 900 KB over a residential lane ≈ $0.001/page at DataImpulse rates (~$1/GB) — a default single-page run of 21 listings lands around a tenth of a cent. Five pages / 105 listings ≈ $0.005.

Notes

• Hidden addresses arrive as the literal [PLACEHOLDER] string in the payload; they are normalized to null (with the neighbourhood kept).
• rooms mirrors bedrooms: the platform's own rooms field is usually 0.
• Legacy URL forms (/apartamentos-en-venta/) silently redirect to the canonical grammar; the Actor only emits canonical URLs and refuses off-canonical redirects (an unknown location slug would otherwise silently un-scope the search).
• Tests run offline against fixtures captured live 2026-09-04: python3 -m unittest discover tests (or pytest) from this directory.