/fotocasa/properties

POST /api/fotocasa/properties

Price: 10 credits

Get full Fotocasa real estate property details by property id (or property URL): title, property and transaction type, price, price drop and price per m², living and land surface, number of rooms and bathrooms, floor, condition, antiquity, orientation, heating, furnished flag, energy and emissions classes, full description, features, address (street, neighborhood, district, municipality, province, zip code and coordinates), photos and the listing agency.

How to use it

Fetch a single Fotocasa property (vivienda) by numeric property id or a property URL. Returns one item with id, url, title, property_type, transaction_type, construction_type, description, price, price_drop, price_per_m2, surface, land_surface, room_count, bathroom_count, floor, condition, antiquity, orientation, heating, is_furnished, energy_class, emissions_class, is_auctioned, is_bare_ownership, is_occupied, is_rented_with_tenants, is_temporary_rental, has_quality_seal, created_at, features, address (street, street_number, neighborhood, district, municipality, locality, region, province, autonomous_community, country, zip_code, coordinates), images and agency (id, name, alias, type, phone, web, image, publisher_id).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• property string required — Fotocasa property id or a property URL containing it (examples: "189190562", "https://www.fotocasa.es/es/comprar/vivienda/madrid-capital/x/189190562/d"; minLength: 1)

Response

• @type string (default: "FotocasaProperty")
• id string required
• url string nullable
• property_type string nullable
• transaction_type string nullable
• construction_type string nullable
• description string nullable
• price integer nullable
• price_drop integer nullable
• price_per_m2 number nullable
• surface integer nullable
• land_surface integer nullable
• room_count integer nullable
• bathroom_count integer nullable
• floor integer nullable
• condition string nullable
• antiquity string nullable
• orientation string nullable
• heating string nullable
• is_furnished boolean nullable
• energy_class string nullable
• emissions_class string nullable
• is_auctioned boolean nullable
• is_bare_ownership boolean nullable
• is_occupied boolean nullable
• is_rented_with_tenants boolean nullable
• is_temporary_rental boolean nullable
• has_quality_seal boolean nullable
• created_at string nullable
• features array (default: [])
• address object nullable
  • @type string (default: "FotocasaAddress")
  • street string nullable
  • street_number integer nullable
  • neighborhood string nullable
  • district string nullable
  • municipality string nullable
  • locality string nullable
  • region string nullable
  • province string nullable
  • autonomous_community string nullable
  • country string nullable
  • zip_code string nullable
  • coordinates object nullable
    • @type string (default: "FotocasaCoordinates")
    • latitude number nullable
    • longitude number nullable
• images array (default: [])
• agency object nullable
  • @type string (default: "FotocasaPropertyAgency")
  • id string nullable
  • name string nullable
  • alias string nullable
  • type string nullable
  • phone string nullable
  • web string nullable
  • image string nullable
  • publisher_id 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 — Property not found (well-formed but nonexistent or expired property 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.