Compare rental and sale pricing against vacation rental pricing in the same area. Understand supply dynamics and price gaps across the residential spectrum.

Idealista for the residential market, Airbnb for short-stay. Same schema, same geography.
The same field names and formats regardless of source. Load and join without mapping.
| Field | Type | Example |
|---|---|---|
| listing_id | string | 104829371 |
| operation | string | sale | rental | short_stay |
| price_eur | number | 285000 |
| area_m2 | number | 94 |
| price_per_m2 | number | 3031 |
| rooms | number | 3 |
| municipality | string | Valencia |
| lat_lon | string | 39.4699, -0.3763 |
| source | string | idealista |
Every source publishes an open sample dataset. Open it and read real records before deciding anything — no account, no token, no form.
Contact details of private sellers are returned as GDPR Protection. We keep only those of professional advertisers, which are businesses.
A real estate consultancy wants to know, neighbourhood by neighbourhood, when it pays more to put a flat on the vacation market than on a long-term lease. The two markets live on different websites, with different fields and units that do not match: Idealista talks about €/m² and rooms, Airbnb about nightly price and capacity.
With both sources in one schema, the join is done by municipality and area. On one side, price, surface and price per square metre for sale and rent; on the other, nightly price, capacity and ratings. The outcome is a table per area where the team computes the gross yield of each model and spots neighbourhoods where the gap between them is widest.
An investor uses the same base to follow €/m² by area and to find areas with strong vacation demand and a purchase price that is still contained. Repeated weekly or monthly, the extraction forms the historical series behind the model. The normalized schema on this page does not include phone numbers or contact details of private advertisers.
The public Idealista sample is linked above. This table summarises the question each schema field resolves when joining residential with vacation data.
| Field | Question it answers | How it is used |
|---|---|---|
| operation | Sale, rent or vacation? | Separate the three markets and compare them by area |
| price_eur · area_m2 | What does it cost and how big is it? | Compute the €/m² of each listing |
| price_per_m2 | What is the comparable metric? | Rank areas and follow their evolution |
| municipality · rooms | Where is it and what size? | Group by area and typology |
| source | Idealista or Airbnb? | Join residential with vacation |
1 source with fixed countries across 3 countries.
Coverage as stated in each actor’s published documentation, as of 9 November 2026.
Sources by country — Idealista: Spain, Portugal, Italy.
No closed list of countries in their documentation: Airbnb.
Spain, Portugal and Italy, with sale and rental listings. Airbnb adds vacation rental supply. Both sources are delivered with the same schema and a source field.
With separate fields: €/m² for residential sale and rent and nightly price for vacation. The join is done by municipality or area; converting to yield is defined by each team according to its own assumptions.
No. The normalized schema on this page does not include phone numbers or contact details of private advertisers, and private contact data appears as GDPR Protection.
To follow the €/m² of an area, a weekly or monthly extraction is enough. If you watch a development or a specific neighbourhood, you can run it daily. Each extraction is independent and can be scheduled in Apify.
Yes. Tell us the cities, typology and period on the datasets page and we will say what we can deliver, with the residential and vacation join already done if you need it.
We can deliver the Idealista and Airbnb join already prepared by city, or build the extraction around your needs.
Pick your source and launch your first run. Pay per result — no data, no charge.