/zachestnyibiznes/companies/requisites

POST /api/zachestnyibiznes/companies/requisites

Price: 10 credits

Get the official requisites of a Russian company by INN or OGRN: full and short name, INN/OGRN/KPP, statistics codes (OKPO/OKTMO/OKATO/OKOGU/OKOPF/OKFS), tax authority and registration dates, legal address and director — ready for contracts.

How to use it

Fetch official requisites for a Russian legal entity by INN (10/12 digits) or OGRN (13/15 digits), or a company URL. Returns one item with full_name, short_name, inn, ogrn, ogrn_assigned_at, kpp, okpo, oktmo, okato, okogu, okopf, okfs, sme_category, tax_authority, tax_registered_at, cbr_registration_number, cbr_registered_at, pfr_registration_number, pfr_registered_at, fss_registration_number, fss_registered_at, legal_address and director.

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/12 digits) or OGRN (13/15 digits), or a full company URL (examples: "7707083893", "1027700132195"; minLength: 1)

Response

• @type string (default: "ZachestnyibiznesRequisites")
• id string required
• url string required
• full_name string nullable
• short_name string nullable
• inn string nullable
• ogrn string nullable
• ogrn_assigned_at string nullable
• kpp string nullable
• okpo string nullable
• oktmo string nullable
• okato string nullable
• okogu string nullable
• okopf string nullable
• okfs string nullable
• tax_authority string nullable
• tax_registered_at string nullable
• cbr_registration_number string nullable
• cbr_registered_at string nullable
• pfr_registration_number string nullable
• pfr_registered_at string nullable
• fss_registration_number string nullable
• fss_registered_at string nullable
• sme_category string nullable
• legal_address string nullable
• director 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 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.