/immobiliare/properties

POST /api/immobiliare/properties

Price: 20 credits

Get full Immobiliare.it property listing details by listing id (or listing URL): title, property type, contract (sale/rent/auction), category, price and price per m², condition, building year, surface and its breakdown, rooms, bedrooms, bathrooms, floor, elevator, condominium fees, kitchen, energy class and heating, features, address (zone, microzone, city, province, region), coordinates, description, photos with captions, floorplans, virtual tours and the listing agency.

How to use it

Fetch a single Immobiliare.it property (annuncio) by numeric listing id or a listing URL. Returns one item with id, url, title, caption, contract, category, property_type, typology, is_new, is_luxury, is_auction, reference, created_at, updated_at, price, price_per_m2, price_range, condition, availability, building_year, surface, surface_breakdown, rooms, bedrooms, bathrooms, floor, total_floors, has_elevator, condo_fees, kitchen, energy (energy_class, heating, air_conditioning, epi), features, address, zone, microzone, city, province, region, latitude, longitude, description, photos (caption/url), floorplans, virtual_tours and agency (id, name, phone, url, image, agent_name, agent_phone).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Immobiliare.it listing id or a listing URL containing it (examples: "129504906", "https://www.immobiliare.it/annunci/129504906/"; minLength: 1)

Response

• @type string (default: "ImmobiliareProperty")
• id integer required
• url string nullable
• caption string nullable
• contract string nullable
• category string nullable
• property_type string nullable
• typology string nullable
• is_new boolean nullable
• is_luxury boolean nullable
• is_auction boolean nullable
• reference string nullable
• created_at integer nullable
• updated_at integer nullable
• price integer nullable
• price_per_m2 number nullable
• price_range string nullable
• condition string nullable
• availability string nullable
• building_year integer nullable
• surface number nullable
• surface_breakdown array (default: [])
  • @type string (default: "ImmobiliareSurfacePart")
  • constitution string nullable
  • surface string nullable
  • commercial_surface string nullable
  • percentage integer nullable
  • floor string nullable
  • surface_type string nullable
• rooms integer nullable
• bedrooms integer nullable
• bathrooms integer nullable
• floor string nullable
• total_floors integer nullable
• has_elevator boolean nullable
• condo_fees string nullable
• kitchen string nullable
• energy object nullable
  • @type string (default: "ImmobiliareEnergy")
  • energy_class string nullable
  • heating string nullable
  • air_conditioning string nullable
  • epi number nullable
  • epi_unit string nullable
  • is_zero_energy_building boolean nullable
• features array (default: [])
• address string nullable
• zone string nullable
• microzone string nullable
• city string nullable
• province string nullable
• region string nullable
• latitude number nullable
• longitude number nullable
• description string nullable
• photos array (default: [])
  • @type string (default: "ImmobiliarePhoto")
  • caption string nullable
  • url string nullable
• floorplans array (default: [])
• virtual_tours array (default: [])
• agency object nullable
  • @type string (default: "ImmobiliareAgency")
  • id integer nullable
  • name string nullable
  • label string nullable
  • phone string nullable
  • url string nullable
  • image string nullable
  • agent_name string nullable
  • agent_phone string nullable

Errors

• 422 — 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 (well-formed but nonexistent or expired listing id) 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.