/zachestnyibiznes/companies

POST /api/zachestnyibiznes/companies

Price: 10 credits

Get a Russian company or sole proprietor (FNS/EGRUL/EGRIP registry) by INN or OGRN: name, full legal name, status, INN/OGRN/KPP/OKPO, registration dates, region and address, charter capital, primary activity (OKVED), director, share registrar and contacts.

How to use it

Fetch a single Russian legal entity or sole proprietor by INN (10/12 digits) or OGRN (13/15 digits), or a full company URL. Returns one item with name, full_name (legal name), status, inn, ogrn, kpp, okpo, registered_at, ogrn_assigned_at, dissolved_at, region, address, postal_code, locality, charter_capital, tax_mode, main_activity (OKVED code+name), director, registrar and contacts (phone/email/website).

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 for legal entity, 12 for sole proprietor) or OGRN (13 digits for legal entity, 15 for sole proprietor), or a full company URL (examples: "7707083893", "1027700132195", "https://zachestnyibiznes.ru/company/ul/1027700132195_7707083893"; minLength: 1)

Response

• @type string (default: "ZachestnyibiznesCompany")
• id string required
• url string required
• company_type string required
• name string nullable
• full_name string nullable
• status string nullable
• inn string nullable
• ogrn string nullable
• kpp string nullable
• okpo string nullable
• registered_at string nullable
• ogrn_assigned_at string nullable
• dissolved_at string nullable
• region string nullable
• address string nullable
• postal_code string nullable
• locality string nullable
• charter_capital integer nullable
• tax_mode string nullable
• main_activity object nullable
  • @type string (default: "ZachestnyibiznesActivity")
  • code string nullable
  • name string nullable
• activities array (default: [])
  • @type string (default: "ZachestnyibiznesActivity")
  • code string nullable
  • name string nullable
• director object nullable
  • @type string (default: "ZachestnyibiznesPerson")
  • name string nullable
  • inn string nullable
  • role string nullable
  • since_at string nullable
• registrar object nullable
  • @type string (default: "ZachestnyibiznesRegistrar")
  • name string nullable
  • inn string nullable
  • ogrn string nullable
• phone string nullable
• email string nullable
• website 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.