POST /api/konturfocus/companies
Price: 20 credits
Get the registry card of a Russian company by INN or OGRN: legal name, status, registration date, tax registration date, small/medium-enterprise (SME) registry status and category, legal address, tax authority, share-register holder, charter capital, primary economic activity (OKVED) and statistics codes (OKPO, OKATO, OKTMO, OKOPF, OKOGU, OKFS).
Look up a Russian legal entity by INN (10/12 digits), OGRN (13/15 digits) or a Kontur.Focus entity URL. Returns one company card with id (OGRN), inn, kpp, ogrn, name, status, reg_date, tax_reg_date, is_msp (in the small/medium-enterprise registry), enterprise_category (Микропредприятие / Малое предприятие / Среднее предприятие), address, postal_code, tax_authority, registrar (share-register holder), capital (RUB), main_activity / main_activity_code (primary OKVED), activity_count and statistics codes (okpo, okato, oktmo, okopf, okogu, okfs, sfr).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — Company INN (10/12 digits), OGRN (13/15 digits) or a Kontur.Focus entity URL (examples: "1027700132195", "7707083893"; minLength: 1)@type string (default: "KonturfocusCompany")id string requiredlegal_entity_type string requiredinn string nullablekpp string nullableogrn string requiredname string nullablestatus string nullablereg_date string nullabletax_reg_date string nullableis_msp boolean (default: false)enterprise_category string nullableaddress string nullablepostal_code string nullabletax_authority string nullableregistrar string nullablecapital integer nullablemain_activity string nullablemain_activity_code string nullableactivity_count integer nullableokpo string nullableokato string nullableoktmo string nullableokopf string nullableokogu string nullableokfs string nullablesfr string nullableurl string required422 — 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 — Company not found in the official registers 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.