/yandexrealty/offers

POST /api/yandexrealty/offers

Price: 20 credits

Get full Yandex Realty offer (listing) details by offer id or offer URL: deal type, property category, price and price per square meter, rooms, total/living/kitchen area, room areas, floor, ceiling height, renovation, bathroom, balcony, window view, building year/type/series, address, coordinates, nearby metro stations, photos, tags, the seller (agency/agent) and the price history.

How to use it

Fetch a single Yandex Realty offer by numeric offer id or an offer URL. Returns one item with id, url, offer_type (SELL/RENT), offer_category (APARTMENT/ROOMS/HOUSE/LOT/GARAGE/COMMERCIAL), flat_type, deal_status, description, created_at, updated_at, price (numeric), price_per_meter, currency, price_trend, rooms_total, area, living_space, kitchen_space, room_spaces, ceiling_height, floor, floors_total, renovation, bathroom_unit, balcony_type, window_view, is_apartments, is_open_plan, is_new_building, is_exclusive, built_year, building_type, building_series, flats_count, porches_count, parking_type, has_lift, has_rubbish_chute, is_guarded, has_security, has_internet, address, latitude, longitude, metro, metro_list (name, transport, time_to_metro, line_color), rgid, view_count, image, images, image_count, tags, author (id, category, name, organization, agent_name, image) and price_history (date, value).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• offer string required — Yandex Realty offer id or an offer URL containing it (examples: "7035113340557150178", "https://realty.yandex.ru/offer/7035113340557150178/"; minLength: 1)

Response

• @type string (default: "YandexrealtyOffer")
• id string required
• url string nullable
• offer_type string nullable
• offer_category string nullable
• flat_type string nullable
• deal_status string nullable
• trust string nullable
• description string nullable
• created_at string nullable
• updated_at string nullable
• price integer nullable
• price_per_meter integer nullable
• currency string nullable
• price_trend string nullable
• rooms_total integer nullable
• area number nullable
• living_space number nullable
• kitchen_space number nullable
• room_spaces array (default: [])
• ceiling_height number nullable
• floor integer nullable
• floors_total integer nullable
• renovation string nullable
• bathroom_unit string nullable
• balcony_type string nullable
• window_view string nullable
• is_apartments boolean nullable
• is_open_plan boolean nullable
• is_new_building boolean nullable
• is_exclusive boolean nullable
• built_year integer nullable
• building_type string nullable
• building_series string nullable
• building_id string nullable
• flats_count integer nullable
• porches_count integer nullable
• parking_type string nullable
• address string nullable
• latitude number nullable
• longitude number 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
• rgid integer nullable
• view_count integer nullable
• has_lift boolean nullable
• has_rubbish_chute boolean nullable
• is_guarded boolean nullable
• has_security boolean nullable
• has_internet boolean nullable
• image string nullable
• images array (default: [])
• image_count integer nullable
• tags array (default: [])
• author object nullable
  • @type string (default: "YandexrealtyOfferAuthor")
  • id string nullable
  • category string nullable
  • name string nullable
  • organization string nullable
  • agent_name string nullable
  • image string nullable
  • created_at string nullable
• price_history array (default: [])
  • @type string (default: "YandexrealtyPricePoint")
  • date string nullable
  • value integer 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 — Offer not found, expired or removed (well-formed but nonexistent/withdrawn offer 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.