/yandexrealty/developers

POST /api/yandexrealty/developers

Price: 20 credits

Get Yandex Realty developer (builder) details by developer id or developer URL: name, description, logo, website, founding date, portfolio statistics (total/finished/unfinished houses and residential complexes), per-region presence, the developer's current region statistics and awards.

How to use it

Fetch a single Yandex Realty developer (застройщик / builder) by numeric developer id or a developer URL. Returns one item with id, url, name, description, long_description, image, web_url, born_at, all_houses, all_sites, finished_houses, finished_sites, unfinished_houses, unfinished_sites, current_region, current_region_sites, current_region_offers, current_region_min_price, region_stats (name, rgid, total_sites) and rewards (year, name, description, image).

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)

Response

• @type string (default: "YandexrealtyDeveloper")
• id string required
• url string nullable
• name string nullable
• description string nullable
• long_description string nullable
• image string nullable
• web_url string nullable
• born_at string nullable
• all_houses integer nullable
• all_sites integer nullable
• finished_houses integer nullable
• finished_sites integer nullable
• unfinished_houses integer nullable
• unfinished_sites integer nullable
• current_region string nullable
• current_region_sites integer nullable
• current_region_offers integer nullable
• current_region_min_price integer nullable
• region_stats array (default: [])
  • @type string (default: "YandexrealtyDeveloperRegionStat")
  • name string required
  • rgid string nullable
  • total_sites integer nullable
• rewards array (default: [])
  • @type string (default: "YandexrealtyDeveloperReward")
  • year integer nullable
  • name string nullable
  • description string nullable
  • image 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 — Developer not found (well-formed but nonexistent developer 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.