Habitaclia Scraper
Pricing
from $3.00 / 1,000 results
Habitaclia Scraper
Extract real estate listings from habitaclia.com — one of Spain's leading property portals.
Pricing
from $3.00 / 1,000 results
Rating
0.0
(0)
Developer
Denys
Maintained by CommunityActor stats
0
Bookmarked
4
Total users
0
Monthly active users
4 days ago
Last modified
Categories
Features
Share
What does Habitaclia Scraper do?
Habitaclia Scraper extracts real estate listings from habitaclia.com, one of Spain's leading property portals. Give it any search result page URL with your filters applied and it returns structured records: price, price per m², area, rooms, address and coordinates, agency details, images, features, energy certificate and price history.
Run it from the Apify Console or the API, schedule it, and send results to your tools through Apify integrations.
Why use Habitaclia Scraper?
- Price monitoring: track asking prices and price drops in a neighbourhood over time.
- Market analysis: compare price per m² across districts, property types and sale vs. rent.
- Lead generation: build lists of real estate agencies active in a region.
- Alerts: schedule a run every day and get notified about new listings matching your search.
How to scrape habitaclia.com listings
- Open habitaclia.com, run a search and apply your filters (property type, location, price…).
- Copy the URL from the address bar.
- In the Input tab, paste it into Start URLs. Add as many search URLs as you need.
- Set Max results per URL (0 collects every listing of the search).
- Click Start, then open the Output tab when the run finishes.
Input
| Field | Type | Description | Default |
|---|---|---|---|
startUrls | Array | Habitaclia search result page URLs | required |
maxResults | Integer | Maximum listings collected from each start URL; 0 = all | 100 |
Example input:
{"startUrls": [{ "url": "https://www.habitaclia.com/pisos-barcelona.htm" },{ "url": "https://www.habitaclia.com/locales_comerciales-en-alt_penedes.htm" }],"maxResults": 200}
Output
Each listing is stored as one item in the default dataset. A shortened example:
{"id": "i52292000000462","url": "https://www.habitaclia.com/a/933b279b-5965-46a5-8847-a0a484eb9055","title": "PISO EN GRACIA CON BALCÓN","propertyType": "FLAT","transaction": "BUY","price": 385000,"area": 70,"pricePerM2": 5500,"rooms": 2,"location": "Carrer de Francisco Giner, Barcelona Capital","city": "Barcelona Capital","coordinates": { "lat": 41.3998, "lon": 2.1580 },"imageUrl": "https://static.fotocasa.es/images/ads/84fb7291-…","agencyName": "…","esParticular": false,"lastUpdated": "2026-11-13T20:42:16.1414481+01:00","scrapedAt": "2026-11-15T21:05:24.000Z","startUrl": "https://www.habitaclia.com/pisos-barcelona.htm","status": "ok"}
Every record has a status. Listings carry "ok" and the startUrl they were found from. A start URL that produced no listings, because it is not a habitaclia URL or habitaclia could not be scraped, is stored as one record with the reason, and the other URLs are still scraped:
{"startUrl": "https://www.habitaclia.com/locales_comerciales-en-alt_penedes.htm","status": "scraping failed: Listings API responded with 400"}
If pagination stops partway through a search, the listings collected so far are kept and one extra record says so:
{"startUrl": "https://www.habitaclia.com/pisos-barcelona.htm","status": "incomplete: pagination stopped after 300 listings: Listings API responded with 403"}
Filter by status to separate listings from these records. The run itself fails only when the scraping service is unreachable.
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Data fields
| Field | Description |
|---|---|
status | ok for listings, otherwise why a start URL produced no or only some listings |
startUrl | Search URL the listing was found from |
id / realEstateAdId | Habitaclia listing ID / internal ad UUID |
url | Direct link to the listing |
title / description | Listing title and description |
propertyType / propertySubtype | Property category, e.g. FLAT, COMMERCIAL_PREMISES |
transaction | BUY or RENT |
price / pricePerM2 | Asking price and price per m² in EUR (null when hidden) |
priceReduction / priceHistory | Last price change and full price history |
area / rooms / bathrooms | Built area in m², rooms, bathrooms |
location / street / city / district / province / zipCode | Address |
coordinates | Latitude and longitude |
features / featuresMissing | Extras the property has or lacks |
energyCertificate | Energy efficiency certificate |
imageUrl / images / imageCount | Main photo, all photos, photo count |
agencyName / agencyUrl / publisher | Listing agency |
esParticular | true for private sellers, false for agencies |
createdAt / lastUpdated | Created / last updated on habitaclia |
scrapedAt | When the data was collected |
How much does it cost to scrape habitaclia?
The Actor itself only waits for results, so it uses very little memory and compute. The Apify free tier is enough to try it out and for small regular runs.
Tips
- Apply filters on habitaclia before copying the URL: narrow searches are faster and give more relevant data.
- With Max results per URL set to
0, large searches can take a long time; make sure the run timeout is long enough. - If one URL fails, the others still complete; its record in the dataset tells you why.
FAQ and support
Is it legal to scrape habitaclia.com? The Actor collects publicly available listing data. Listings can include personal data such as agent names and phone numbers; make sure you have a legitimate purpose for processing it under GDPR, and follow habitaclia's Terms of Service.
The run returned no results. Why? Habitaclia sometimes blocks requests temporarily. Run it again; if the problem persists, report it.
For bugs or feature requests, open an issue in the Issues tab. Custom solutions are available on request.