/rmsp/companies/search

POST /api/rmsp/companies/search

Price: 5 credits

Search the Russian SME register (Federal Tax Service) by name, owner, region, activity (OKVED) and other criteria. Returns each matching subject's INN, OGRN, name, type (legal entity or sole proprietor), SME category, registry status and dates, region/locality, main activity, headcount and registry flags. Provide a query or a region.

How to use it

Find Russian SME-register subjects by keyword and filters. Provide query (name / owner / partial INN) or region (one is required), plus optional np_type (UL/IP), okved, registered_at (DD.MM.YYYY), and the is_new / is_social / has_licenses / is_hitech / is_partnership flags. Sort with sort_field and sort.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string — Name, owner full name or partial INN to search for (default: ""; examples: "кафе", "ромашка")
• count integer required — Max number of results to return (min: 1)
• np_type string nullable — Restrict to legal entities (UL) or sole proprietors (IP) (one of: "UL", "IP")
• region string nullable — Restrict to a Russian region (required when no query is given) (one of: "01", "02", "03", "04", "05", "06", "07", "08", "09", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24", "25", "26", "27", "28", "29", "30", "31", "32", "33", "34", "35", "36", "37", "38", "39", "40", "41", "42", "43", "44", "45", "46", "47", "48", "49", "50", "51", "52", "53", "54", "55", "56", "57", "58", "59", "60", "61", "62", "63", "64", "65", "66", "67", "68", "69", "70", "71", "72", "73", "74", "75", "76", "77", "78", "79", "83", "86", "87", "89", "90", "91", "92", "93", "94", "95", "99")
• district string nullable — 13-digit KLADR district code (within the selected region)
• city string nullable — 13-digit KLADR city code (within the selected district)
• locality string nullable — 13-digit KLADR locality code (within the selected city)
• okved string nullable — Main OKVED activity code (e.g. 56.10) (examples: "56.10", "62.01")
• registered_at string nullable — Registration date in DD.MM.YYYY format (examples: "10.10.2022")
• is_new boolean nullable — Only newly created subjects
• is_social boolean nullable — Only social enterprises
• has_licenses boolean nullable — Only subjects holding licenses
• is_hitech boolean nullable — Only producers of innovative / high-tech products
• is_partnership boolean nullable — Only participants in partnership programs
• sort_field string — Field to sort results by (default: "NAME_EX"; one of: "NAME_EX", "INN", "DTREGISTRY", "CATEGORY")
• sort string — Sort direction (default: "ASC"; one of: "ASC", "DESC")

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 — The entity was not found, or a precondition failed 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.