7 days trial then $28.00/month - No credit card required now
Since Idealista doesn't provide an API this actor should help you to retrieve data from it.
The Idealista data scraper supports the following features:
Scrape property details - You can scrape attributes like property images, price, features, neighborhood, nearby schools and many more. You can find details below.
Scrape sold properties - You can scrape sold properties through a search list.
Scrape for sale properties - If you are looking for a property which is for sale, you can directly target them.
Scrape rental properties - Rental properties can be directly targeted.
Scrape by keyword - You can use location-wise keywords to search specific search lists. Also you can directly point out rental, for sale or sold properties on this feature.
Scrape properties by filter - Auto detection of URLs helps you to directly copy/paste the URLs into the scraper to apply any filtering you like.
The input of this scraper should be JSON containing the list of pages on Realtor that should be visited. Required fields are:
|(optional) List of Idealista URLs. You should only provide property detail or search URLs
|(optional) You can limit scraped products. This should be useful when you search through the big subcategories.
|(optional) Final number of page that you want to scrape. Default is
|(optional) Keyword that can be searched in Realtor search engine. When it is present,
mode must be used as well.
|(optional) Mode of the actor. It gets the keyword from
search parameter and initiate the search according to the mode. Can be
SOLD. When present,
search must be provided as well.
|(optional) Function that takes a JQuery handle ($) as argument and returns object with data
This solution requires the use of Proxy servers, either your own proxy servers or you can use Apify Proxy.
When you want to have a filtering over a search URL; go to Idealista, create filters over the serach list and copy and paste the link as one of the startUrl.
The actor optimized to run blazing fast and scrape many as properties as possible. Therefore, it forefronts all property detail requests. If actor doesn't block very often it'll scrape 50 properties in 2 minutes with ~0.05-0.07 compute units.