POST /api/idealista/properties
Price: 10 credits
Get a single Idealista property listing (Portugal or Italy) by id or listing URL: title, location, sale or rent operation, asking price with the previous price and discount when the seller has cut it, price per m², gross and usable floor area, rooms, bathrooms, condition, construction year, energy rating, the full advertiser description, the specification lists shown on the page, photo and video URLs with per-media-type counts, and the listing agency with its AMI licence number.
Portugal and Italy only — set `domain` to pt (idealista.pt, the default) or it (idealista.it). Spain is not covered, and the two id spaces are separate, so a Portuguese id with domain=it answers 412. Prices are in euros; `price` is the asking price for a sale and the monthly rent for a rental, so read `operation` before comparing figures. `previous_price` appears only on listings the seller actually discounted, so its absence means no recorded cut, not an unchanged price. Withdrawn listings are removed rather than archived and answer 412, which is normal for older ids. `room_count` counts what the local portal counts: bedrooms in Portugal (T2 = 2), total rooms in Italy (trilocale = 3). A new development (`property_type` new_development) describes a whole project rather than one unit, so its `price` is the cheapest unit on offer ('Preço desde' / 'Prezzo da') and it states no floor area, room or bathroom count. An Italian room let (`property_type` room) advertises one bed in a shared flat, so `surface`, `room_count` and `bathroom_count` describe the whole flat and `price_per_m2` — room rent over the flat's area — is not a meaningful figure. Exact coordinates are not published; `location` is a neighbourhood-level description.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)domain string — Country site the listing belongs to: pt = idealista.pt, it = idealista.it (default: "pt"; one of: "pt", "it")property string required — Idealista listing id, or a listing URL containing it. Accepts individual properties (/imovel/ on pt, /immobile/ on it) and new developments (/empreendimento/ on pt, /nuova-costruzione/ on it) (examples: "35081413", "https://www.idealista.pt/imovel/35081413/", "https://www.idealista.it/immobile/34841613/"; minLength: 1)@type string (default: "IdealistaProperty")id string requiredurl string nullablelisting_title string nullablelocation string nullablelocation_id string nullableproperty_type string nullableoperation string nullableprice number nullableprevious_price number nullableprice_drop_percent integer nullableprice_per_m2 number nullablesurface integer nullableusable_surface integer nullableroom_count integer nullablebathroom_count integer nullablefloor string nullablehas_elevator boolean nullablecondition string nullableyear_built integer nullableenergy_rating string nullablereference string nullabledescription string nullablefeatures array (default: [])building_features array (default: [])media object nullable@type string (default: "IdealistaMediaCounts")images integer nullablefloor_plans integer nullablevideos integer nullablevirtual_tours integer nullablehome_staging integer nullableimages array (default: [])floor_plan_images array (default: [])videos array (default: [])agency object nullable@type string (default: "IdealistaAgency")name string nullableurl string nullableimage string nullablelicence string nullableis_professional boolean nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Listing not found: a well-formed id that is expired, withdrawn, never existed, or belongs to the other country's site Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.