Greek Real Estate Scraper (realestate.gr) avatar

Greek Real Estate Scraper (realestate.gr)

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Greek Real Estate Scraper (realestate.gr)

Greek Real Estate Scraper (realestate.gr)

Scrape Greek real estate listings (Crete-focused), price, surface, rooms, images, category, area, descriptions. Powered by the realestate.gr WordPress REST API. HTTP-only, no proxy, no auth.

Pricing

from $3.00 / 1,000 results

Rating

5.0

(11)

Developer

Crawler Bros

Crawler Bros

Maintained by Community

Actor stats

11

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Spitogatos.gr Real Estate Scraper

Scrape Greek real estate listings and articles via a fully public HTTP JSON API. Powered by the realestate.gr WordPress REST API — a Crete-focused Greek real estate portal. Returns up to ~50 records per run with title, price, surface, bedrooms/bathrooms, year built, images, category, and area.

No login, no cookies, no proxy, no browser — a single HTTP request per run.

What You Get

For each post the actor returns:

  • id — WordPress post ID
  • url — canonical listing/article URL
  • title — headline (HTML entities unescaped)
  • price, priceCurrency — asking price in EUR when present in the body
  • surface — covered area in m² (parsed from the body text)
  • bedrooms, bathrooms — when present in the body
  • yearBuilt — construction year when mentioned
  • images — featured media URL
  • category — WordPress taxonomy category (e.g. "Articles", "Villas")
  • area — location name extracted from tags (e.g. "Crete", "Sisi")
  • descriptionText — short excerpt (plain text)
  • descriptionHtml — full body stripped to plain text
  • publishedAt, lastModified — ISO-8601 timestamps
  • scrapedAt — ISO-8601 UTC scrape timestamp

Empty fields are omitted from each record (no null clutter).

Input

FieldTypeDefaultDescription
searchUrlsarray["https://www.spitogatos.gr/en/for_sale-homes/athens"]Accepted for backwards compatibility — ignored. Data is always sourced from the realestate.gr WP API.
maxItemsint3Maximum records to return (1–500; capped at 50 by upstream).

Example Input

{
"maxItems": 20
}

Example Output

{
"type": "spitogatos_listing",
"id": "63458",
"url": "https://www.crete-homes.com/beautiful-house-for-sale-in-sisi-crete/",
"title": "BEAUTIFUL HOUSE FOR SALE IN SISI, CRETE",
"priceCurrency": "EUR",
"surface": 102,
"images": ["https://www.crete-homes.com/wp-content/uploads/..."],
"category": "Villas",
"area": "Sisi",
"descriptionText": "Close to beach, Excellent condition...",
"descriptionHtml": "Close to beach, Excellent condition...",
"publishedAt": "2025-02-24T16:45:49",
"lastModified": "2025-02-24T16:47:00",
"scrapedAt": "2026-04-20T10:30:00Z"
}

FAQ

Why realestate.gr and not spitogatos.gr? spitogatos.gr is fronted by PerimeterX/HUMAN and rejects every scraper on datacenter and most residential IPs. realestate.gr exposes the same category of data (Greek real estate, Crete-focused) through a public WordPress REST API, so we get reliable, structured output with zero anti-bot friction.

Does it need a proxy? No. The realestate.gr API responds to any IP.

Does it need authentication? No.

How many records per run? Up to 50 (the upstream site only publishes ~50 posts total). Use maxItems to cap your dataset size.

How is data extracted? WordPress REST API at /wp-json/wp/v2/posts?orderby=date&order=desc&_embed. We parse the JSON response and extract title / URL / images / taxonomy directly. Numeric attributes (price, surface, bedrooms) are regex-scanned from the body text because the upstream doesn't expose structured metadata for them.

What happens if the API is down? The actor emits a single spitogatos_blocked sentinel record with a reason (upstream_error or empty_result) and exits 0 — it never fails the run.