/rmsp/companies

POST /api/rmsp/companies

Price: 1 credit

Look up a Russian SME-register subject by its INN, OGRN or OGRNIP in the Federal Tax Service's Register of Small and Medium-sized Enterprises: registered name, subject type (legal entity or sole proprietor), SME category (micro/small/medium), registry status and registration dates, main activity (OKVED) code and name, region and locality, average headcount, and registry flags (newly created, social enterprise, support recipient, licenses, contracts, high-tech, partnership).

How to use it

Check whether a Russian company or sole proprietor is in the official SME register and get its category. Accepts an INN (10-digit for a legal entity, 12-digit for a sole proprietor), OGRN (13-digit) or OGRNIP (15-digit). Returns name, np_type, category (micro/small/medium), is_active, registered_at, region, okved and headcount.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — INN (10 or 12 digits), OGRN (13 digits) or OGRNIP (15 digits) (examples: "4707048043", "1224700016750", "321861700091274")

Response

• @type string (default: "RmspCompany")
• inn string required
• ogrn string required
• name string required
• np_type string required (one of: "UL", "IP")
• category string nullable (one of: "1", "2", "3")
• category_name string nullable
• is_active boolean (default: false)
• is_new boolean (default: false)
• is_social boolean (default: false)
• is_support_recipient boolean (default: false)
• has_licenses boolean (default: false)
• has_contracts boolean (default: false)
• is_hitech boolean (default: false)
• is_partnership boolean (default: false)
• registered_at string nullable
• excluded_at string nullable
• region_code string nullable
• region string nullable
• area string nullable
• city string nullable
• locality string nullable
• okved string nullable
• okved_name string nullable
• employee_count integer nullable
• phone string nullable
• email string nullable
• web_url 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 — No SME-register subject matches this INN/OGRN/OGRNIP (the subject is not in the register) 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.