POST /api/rusprofile/companies/inspections
Price: 20 credits
Get government inspections of a Russian company, each in full: inspection number and date, status, type, result, period, form, basis and the supervising authority. For most companies the answer holds one inspection, the first of the list; for other companies it holds the list in order, up to count (at most 100).
Most companies return one inspection, the first of their list, so a one-row answer is not necessarily the company's full list of inspections; other companies return the list up to count. Pass the company as INN, OGRN, Rusprofile id or URL.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — Company INN, OGRN, internal Rusprofile id or company URL (examples: "7707083893", "1027700132195", "2835629", "https://www.rusprofile.ru/id/2835629"; minLength: 1)count integer required — Max number of results (min: 1; max: 100)@type string (default: "RusprofileInspection")number string nullablerecord_date integer nullablestatus string nullableinspection_type string nullableresult string nullablestart_date integer nullableend_date integer nullableduration string nullableform string nullableaddress string nullablebasis string nullableauthority string nullabledetails array (default: [])@type string (default: "RusprofileDetail")section string nullablelabel string nullablevalue string nullable422 — 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 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.