/yandexrealty/sites

POST /api/yandexrealty/sites

Price: 20 credits

Get full Yandex Realty new building (residential complex) details by site id or new building URL: name, developer, price range and price per square meter, area range, building class, floors, total apartments, construction state and delivery dates, interior finish, parking, room offers by room type (price, area, offer count), transaction terms (mortgage/installment), address, coordinates, review count and rating, description and photos.

How to use it

Fetch a single Yandex Realty new building (ЖК / residential complex) by numeric site id or a new building URL. Returns one item with id, url, name, full_name, description, flat_status, construction_state, site_type, building_class (ECONOM/COMFORT/COMFORT_PLUS/BUSINESS/ELITE), wall_type (wall material, e.g. MONOLIT/BRICK/PANEL), is_apartment, total_floors, min_total_floors, total_apartments, ceiling_height, interior_finish, parking_type, price_from, price_to, price_per_meter_min/max, currency, area_min/max, total_offers, resale_total_offers, has_mortgage, has_installment, has_maternity_funds, is_fz214 (sold under the 214-FZ shared-construction law), agreement_type, address, latitude, longitude, rgid, distance_from_ring_road, metro (name, transport, time_to_metro, line_color), metro_list, review_count, review_rating, image, images, developer (id, name, legal_name, image, url, born_at, finished_sites, unfinished_sites), room_offers (room_type, price_from, price_to, area_from, area_to, offer_count, status) and delivery_dates (year, quarter, phase_name, house_count, is_finished).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• site string required — Yandex Realty new building (site) id or a new building URL containing it (examples: "375274", "https://realty.yandex.ru/moskva/kupit/novostrojka/salarevo-park-375274/"; minLength: 1)

Response

• @type string (default: "YandexrealtySite")
• id string required
• url string nullable
• name string nullable
• full_name string nullable
• description string nullable
• flat_status string nullable
• construction_state string nullable
• site_type string nullable
• building_class string nullable
• wall_type string nullable
• is_apartment boolean nullable
• total_floors integer nullable
• min_total_floors integer nullable
• total_apartments integer nullable
• ceiling_height integer nullable
• interior_finish string nullable
• parking_type string nullable
• price_from integer nullable
• price_to integer nullable
• price_per_meter_min integer nullable
• price_per_meter_max integer nullable
• currency string nullable
• area_min number nullable
• area_max number nullable
• total_offers integer nullable
• resale_total_offers integer nullable
• has_mortgage boolean nullable
• has_installment boolean nullable
• has_maternity_funds boolean nullable
• is_fz214 boolean nullable
• agreement_type string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• rgid integer nullable
• distance_from_ring_road integer nullable
• metro object nullable
  • @type string (default: "YandexrealtyMetro")
  • name string required
  • transport string nullable
  • time_to_metro integer nullable
  • line_color string nullable
• metro_list array (default: [])
  • @type string (default: "YandexrealtyMetro")
  • name string required
  • transport string nullable
  • time_to_metro integer nullable
  • line_color string nullable
• review_count integer nullable
• review_rating number nullable
• image string nullable
• images array (default: [])
• developer object nullable
  • @type string (default: "YandexrealtySiteDeveloper")
  • id string nullable
  • name string nullable
  • legal_name string nullable
  • image string nullable
  • url string nullable
  • born_at string nullable
  • finished_sites integer nullable
  • unfinished_sites integer nullable
• room_offers array (default: [])
  • @type string (default: "YandexrealtySiteRoomOffer")
  • room_type string required
  • price_from integer nullable
  • price_to integer nullable
  • area_from number nullable
  • area_to number nullable
  • offer_count integer nullable
  • status string nullable
• delivery_dates array (default: [])
  • @type string (default: "YandexrealtySiteDeliveryDate")
  • year integer nullable
  • quarter integer nullable
  • phase_name string nullable
  • house_count integer nullable
  • is_finished boolean 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 — New building not found (well-formed but nonexistent site 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.