# /listorg/companies/search

`POST /api/listorg/companies/search`

Price: 1 credit

Search Russian companies (FNS/EGRUL registry) by name, INN, OGRN, OKPO, director/founder, phone, address or bank BIC, with filters by active status, presence/activity of a sole proprietor (ИП), prefix matching, historical data, presence of contacts/branches, activity (OKVED), region (OKATO), ownership form (OKFS), government authority (OKOGU), and ranges on headcount, revenue, profit, assets and registration date, plus configurable sort order.

## How to use it

Search the Russian company registry. Provide query and count. type selects the matched field (all/name/inn/ogrn/okpo/director_founder/phone/address/bank_bic). Optional filters: sort, active_only, has_sole_proprietor, active_sole_proprietor, prefix_match, include_historical, with_phone, with_website, with_email, with_branches, okved, okato, okfs, okogu, employees_min/max, revenue_min/max, profit_min/max, assets_min/max (thousand RUB), registered_after/before (YYYY-MM-DD). Each result has id (internal), url, name, full_name, status, is_active, inn, kpp, director, address.

## 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 string (company name, INN, OGRN, address, director, etc.) (minLength: 1)
- `count` (integer, required) — Max number of results to return (min: 1)
- `type` (string) — Which field the query is matched against (default: "all"; one of: "all", "name", "inn", "ogrn", "okpo", "director_founder", "phone", "address", "bank_bic")
- `sort` (string) — Result ordering (default: "relevance"; one of: "relevance", "popularity", "registration_desc", "registration_asc", "employees_desc", "employees_asc", "revenue_desc", "revenue_asc", "profit_desc", "profit_asc", "assets_desc", "assets_asc")
- `active_only` (boolean) — Only currently active organizations (default: false)
- `has_sole_proprietor` (boolean) — Only entries that have a registered sole proprietor (ИП) (default: false)
- `active_sole_proprietor` (boolean) — Only entries with a currently active sole proprietor (ИП) (default: false)
- `prefix_match` (boolean) — Match the query against the beginning of words (default: false)
- `include_historical` (boolean) — Include historical (renamed/former) data in the match (default: false)
- `with_phone` (boolean) — Only organizations that have a phone number (default: false)
- `with_website` (boolean) — Only organizations that have a website (default: false)
- `with_email` (boolean) — Only organizations that have an e-mail (default: false)
- `with_branches` (boolean) — Include branches/subdivisions in results (default: false)
- `okved` (string, nullable) — OKVED v2 activity code filter (e.g. 62.01)
- `okato` (string, nullable) — OKATO region code filter (e.g. 45 = Moscow)
- `okfs` (string, nullable) — OKFS ownership-form code filter (e.g. 16 = private)
- `okogu` (string, nullable) — OKOGU government-authority code filter
- `employees_min` (integer, nullable) — Minimum headcount (min: 0)
- `employees_max` (integer, nullable) — Maximum headcount (min: 0)
- `revenue_min` (integer, nullable) — Minimum annual revenue in thousand RUB (min: 0)
- `revenue_max` (integer, nullable) — Maximum annual revenue in thousand RUB (min: 0)
- `profit_min` (integer, nullable) — Minimum net profit in thousand RUB
- `profit_max` (integer, nullable) — Maximum net profit in thousand RUB
- `assets_min` (integer, nullable) — Minimum capital/assets in thousand RUB (min: 0)
- `assets_max` (integer, nullable) — Maximum capital/assets in thousand RUB (min: 0)
- `registered_after` (string, nullable) — Registered on or after this date (YYYY-MM-DD)
- `registered_before` (string, nullable) — Registered on or before this date (YYYY-MM-DD)

## Response

### 200 — Successful Response

- `@type` (string) (default: "ListorgCompanySearchResult")
- `id` (string, required)
- `url` (string, required)
- `name` (string, nullable)
- `full_name` (string, nullable)
- `status` (string, nullable)
- `is_active` (boolean, nullable)
- `inn` (string, nullable)
- `kpp` (string, nullable)
- `director` (string, nullable)
- `address` (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.