/konturfocus/companies/search

POST /api/konturfocus/companies/search

Price: 5 credits

Search Russian companies and sole proprietors by name, INN, OGRN, address or person name. Optionally filter by region, industry and whether the match is in actual (current) requisites only.

How to use it

Search the Russian company register by free text (name, INN, OGRN, address or person name). Each result has id (OGRN), ogrn, inn, name, raw_name, reg_date, main_activity and address. Filter by region (Russian region) and industry, and set data_status to actual to match only current requisites.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Search query: company name, INN, OGRN, address or person name (examples: "магнит"; minLength: 1)
• count integer required — Number of results to return (min: 1)
• region string nullable — Filter by Russian region (one of: "01", "04", "22", "28", "29", "30", "99", "02", "31", "32", "03", "33", "34", "35", "36", "05", "93", "79", "75", "90", "37", "06", "38", "07", "39", "08", "40", "41", "09", "10", "42", "43", "11", "44", "23", "24", "91", "45", "46", "47", "48", "94", "49", "12", "13", "77", "50", "51", "83", "52", "53", "54", "55", "56", "57", "58", "59", "25", "60", "61", "62", "63", "78", "64", "14", "65", "66", "92", "15", "67", "26", "68", "16", "69", "70", "71", "17", "72", "18", "73", "27", "19", "86", "95", "74", "20", "21", "87", "89", "76")
• industry string nullable — Filter by industry (one of: "sS", "sT", "sM", "sI", "sF", "sZ", "sE", "sK", "sG", "sO", "cT", "cT1", "cT2", "cT3", "cT4", "cU", "cU1", "cU2", "cU3", "cU4", "cU5", "cU6", "cU7", "cU8", "cU9", "cU10", "cP", "cP1", "cP2", "cP3", "cP4", "cP5", "cP6", "cP7", "cP8", "cP9", "cP10", "cP11")
• data_status string — Match in any requisites or only the actual (current) ones (default: "any"; one of: "any", "Actual")

Response

• @type string (default: "KonturfocusSearchResult")
• id string required
• ogrn string required
• inn string nullable
• name string nullable
• raw_name string nullable
• reg_date string nullable
• main_activity string nullable
• address string nullable
• url string required

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.