/rosreestr/objects/search

POST /api/rosreestr/objects/search

Price: 5 credits

Search Russian real-estate objects in the EGRN cadastre by cadastral number or address

How to use it

Search the Russian EGRN cadastre by a cadastral number or a free-text address. Returns a list of matching real-estate objects (land parcels, buildings, premises, parking, structures, complexes, zones) each with its EGRN record — address, area, cadastral value, category, purpose, status, ownership type and geometry. Use the optional category filter to restrict to one object type.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Cadastral number or free-text address to search the EGRN cadastre for (examples: "77:01:0001044:3030", "Москва, Тверская улица, 13", "Краснодар, улица Красная"; minLength: 1)
• count integer required — Number of objects to return (min: 1)
• category string nullable — Restrict results to a single object category (one of: "land_parcel", "building", "premise", "parking", "construction", "incomplete_construction", "complex", "zone")

Response

• @type string (default: "RosreestrObject")
• cad_number string nullable
• category string nullable (one of: "land_parcel", "building", "premise", "parking", "construction", "incomplete_construction", "complex", "zone")
• category_id integer nullable
• category_name string nullable
• type string nullable
• name string nullable
• purpose string nullable
• address string nullable
• status string nullable
• is_removed boolean nullable
• area number nullable
• declared_area number nullable
• specified_area number nullable
• built_up_area number nullable
• cadastral_cost number nullable
• cost_index number nullable
• cost_application_date string nullable
• cost_determination_date string nullable
• cost_registration_date string nullable
• cost_determination_basis string nullable
• floor string nullable
• floors string nullable
• underground_floors string nullable
• year_built string nullable
• year_commissioning string nullable
• degree_readiness string nullable
• extension number nullable
• height number nullable
• depth number nullable
• volume number nullable
• land_category string nullable
• permitted_use string nullable
• ownership_type string nullable
• right_type string nullable
• parent_cad_number string nullable
• quarter_cad_number string nullable
• facility_cad_number string nullable
• included_cad_numbers array (default: [])
• land_cad_numbers array (default: [])
• cadastral_district string nullable
• zone_type string nullable
• boundary_type string nullable
• border_reg_number string nullable
• restrictions string nullable
• legal_act object nullable
  • @type string (default: "RosreestrLegalAct")
  • name string nullable
  • number string nullable
  • act_date string nullable
  • issuer string nullable
• registration_date string nullable
• is_cultural_heritage boolean nullable
• objdoc_id integer nullable
• registers_id integer nullable
• geometry object nullable
  • @type string (default: "RosreestrGeometry")
  • type string required
  • coordinates array nullable
  • crs 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 — The entity was not found, or a precondition failed 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.