/rusprofile/companies

POST /api/rusprofile/companies

Price: 10 credits

Get a Russian company by INN, OGRN or internal id: name, full legal name, status, INN/KPP/OGRN and statistics codes (OKPO/OKATO/OKTMO/OKFS/OKOGU/OKOPF), director, charter capital, registration date, address with region and postal code, primary activity (OKVED) and tax authority.

How to use it

Fetch a single Russian legal entity by INN (10 digits), OGRN (13 digits), internal Rusprofile id or a full company URL. Returns one item with id, url, name, full_name, status, is_active, inn, kpp, ogrn, okpo, okato, oktmo, okfs, okogu, okopf, director, charter_capital (RUB), registered_at (YYYY-MM-DD), postal_code, region, address, main_activity_code, main_activity_name and tax_authority. Use the companies/arbitrations, connections, procurements, general-court-cases and enforcements endpoints for the litigation, affiliation and procurement detail.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company INN (10 digits), OGRN (13 digits), internal Rusprofile id or a full company URL (examples: "7707083893", "1027700132195", "2835629", "https://www.rusprofile.ru/id/2835629"; minLength: 1)

Response

• @type string (default: "RusprofileCompany")
• id string required
• url string required
• name string nullable
• full_name string nullable
• status string nullable
• is_active boolean nullable
• inn string nullable
• kpp string nullable
• ogrn string nullable
• okpo string nullable
• okato string nullable
• oktmo string nullable
• okfs string nullable
• okogu string nullable
• okopf string nullable
• director object nullable
  • @type string (default: "RusprofileDirector")
  • name string nullable
  • position string nullable
  • person_id string nullable
• charter_capital integer nullable
• registered_at string nullable
• postal_code string nullable
• region string nullable
• address string nullable
• main_activity_code string nullable
• main_activity_name string nullable
• tax_authority 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 — Company not found (well-formed INN/OGRN but no matching record in the registry) 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.