/yandexrealty/developers/sites

POST /api/yandexrealty/developers/sites

Price: 20 credits

List the new buildings (residential complexes) of a Yandex Realty developer by developer id or developer URL, within a region. Returns new building cards with name, price range, building class, construction state, address, metro, review rating and photos.

How to use it

List a Yandex Realty developer's new buildings by numeric developer id or a developer URL. region is the site region slug (defaults to moskva_i_moskovskaya_oblast). Each result has id, url, name, full_name, description, building_class, state, has_virtual_tour, price_from, price_to, developer_id, developer_name, address, rgid, metro (name, transport, time_to_metro), review_count, review_rating, image and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• developer string required — Yandex Realty developer id or a developer URL containing it (examples: "52308", "https://realty.yandex.ru/moskva/zastroyschik/pik-52308/"; minLength: 1)
• region string — Region path slug to list the developer's new buildings in (default: "moskva_i_moskovskaya_oblast"; examples: "moskva_i_moskovskaya_oblast", "sankt-peterburg_i_leningradskaya_oblast"; minLength: 1)
• count integer required — Max number of new buildings to return (min: 1)

Response

• @type string (default: "YandexrealtySiteSearchResult")
• id string required
• url string nullable
• name string nullable
• full_name string nullable
• description string nullable
• building_class string nullable
• state string nullable
• has_virtual_tour boolean nullable
• price_from integer nullable
• price_to integer nullable
• developer_id string nullable
• developer_name string nullable
• address string nullable
• rgid integer nullable
• metro object nullable
  • @type string (default: "YandexrealtySiteSearchMetro")
  • name string required
  • transport string nullable
  • time_to_metro integer nullable
• review_count integer nullable
• review_rating number nullable
• image string nullable
• images array (default: [])

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 — Developer not found or has no new buildings in the given region 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.