One API, 2 marketplaces

Idealista and Fotocasa data from one API

Spanish property splits across two portals and the overlap is partial, so pricing a barrio from one of them is pricing half of it. Both sit behind one key here, and Idealista also covers Italy and Portugal from the same engine.

Why not the official API

Idealista runs a request-access API with a low free quota aimed at partners; Fotocasa publishes none. Neither answers the cross-portal question. This reads the public listings of both, no account, one key.

Coverage

What the two engines give you

Idealista
search, detail, geography
Fotocasa
location_search, search, property_detail, agency
Markets
Idealista reaches Spain, Italy and Portugal; Fotocasa is Spain
Agencies
Fotocasa exposes the listing agency as its own record
Worked example

Compare asking prices in one district

Each portal names places its own way, so resolve the area before searching.

  1. 1
    POST /idealista/v1/geography

    district name to Idealista's own area handle

  2. 2
    POST /idealista/v1/search

    listings for that area

  3. 3
    POST /fotocasa/v1/location_search

    the same district on Fotocasa

  4. 4
    POST /fotocasa/v1/search

    listings, then compare the two distributions

Two independent asking-price distributions for the same district.

Before you join them

Where the two sources genuinely differ

 idealistafotocasa
CountriesSpain, Italy, PortugalSpain only
Depth3 actions: search, detail, geography4 actions, including agency
Place lookupgeography endpointlocation_search — different handles, no shared id