# /pbnalog/documents/search

`POST /api/pbnalog/documents/search`

Price: 5 credits

Search registration documents filed with the Russian Federal Tax Service («Прозрачный бизнес») by company OGRN/OGRNIP or applicant name, with optional filters for subject type, application form and submission date range. Returns each document's form code, applicant, tax office, incoming number, submission channel, decision and submission/completion dates — useful for monitoring registration actions such as director, address or reorganization changes.

## How to use it

List registration documents a Russian company or sole proprietor has filed with the tax service. Provide ogrn (OGRN/OGRNIP) or applicant name; optional np_type, form and date_from/date_to (DD.MM.YYYY). Returns form, applicant, tax office, dates and decision.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `ogrn` (string, nullable) — OGRN (13 digits) or OGRNIP (15 digits) whose filed documents to list (examples: "1027700132195")
- `name` (string, nullable) — Applicant name to search filed documents by (examples: "Иванов")
- `count` (integer, required) — Max number of results to return (min: 1)
- `np_type` (string, nullable) — Restrict to legal-entity (ul) or sole-proprietor (ip) documents (one of: "ul", "ip")
- `form` (string, nullable) — Restrict to a specific registration application form code (one of: "Р12003", "Р12016", "Р13014", "Р15016", "Р16002", "Р18002", "Р18003", "Р18004", "Р19001", "Р34001", "Р34002", "Р38001", "Р24001", "Р24002", "Р26001", "Р26002")
- `date_from` (string, nullable) — Earliest submission date (DD.MM.YYYY) (examples: "01.01.2025")
- `date_to` (string, nullable) — Latest submission date (DD.MM.YYYY) (examples: "31.12.2025")

## Response

### 200 — Successful Response

- `@type` (string) (default: "PbnalogDocument")
- `inn` (string, nullable)
- `ogrn` (string, nullable)
- `grn` (string, nullable)
- `np_type` (string, required)
- `form` (string, nullable)
- `applicant` (string, nullable)
- `tax_authority` (string, nullable)
- `incoming_number` (string, nullable)
- `channel` (string, nullable)
- `decision` (string, nullable)
- `submitted_at` (string, nullable)
- `completed_at` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.