/pbnalog/companies/search

POST /api/pbnalog/companies/search

Price: 5 credits

Search Russian legal entities and sole proprietors in the Federal Tax Service's «Прозрачный бизнес» (Transparent Business) service by name, INN, OGRN or OGRNIP, with optional filters for subject type, region, activity (OKVED), legal-entity registry status, sole-proprietor tax regime and SME-register membership. Returns each match's INN, OGRN, name, subject type, status, registration dates, region, main activity and a token for the full company card.

How to use it

Find Russian companies and sole proprietors by name or INN/OGRN/OGRNIP. Optional filters: np_type (ul/ip), region, okved, status (legal entities), tax_mode (sole proprietors), msp_only. Returns name, status, region, activity and a token usable with the companies endpoint.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string — Name, INN, OGRN or OGRNIP to search for (default: ""; examples: "сбербанк", "7707083893", "строй")
• 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 (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")
• okved string nullable — Main OKVED activity code (e.g. 56.10) (examples: "56.10", "62.01")
• status string nullable — Legal-entity registry status (applies to legal entities only) (one of: "10", "20", "30", "40", "50", "60")
• tax_mode string nullable — Applied tax special regime (applies to sole proprietors only) (one of: "10", "20", "30", "40", "50")
• msp_only boolean — Only subjects listed in the SME register (default: false)

Response

• @type string (default: "PbnalogCompanySearchResult")
• inn string required
• ogrn string required
• name string required
• name_short string nullable
• np_type string required
• status string nullable
• status_code string nullable
• is_invalid boolean (default: false)
• registered_at string nullable
• ogrn_date string nullable
• region string nullable
• region_code string nullable
• okved string nullable
• okved_name string nullable
• token 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.