# /gaspravosudie/courts/search

`POST /api/gaspravosudie/courts/search`

Price: 5 credits

Search the directory of Russian federal courts of general jurisdiction within a region: court name, classification code, region, address, phone, email and official website.

## How to use it

List courts of a Russian region. Provide region and count; optionally name to filter by court-name substring. Each result has id (classification code, e.g. 66RS0005), name, region, address, phone, email, website and subdomain.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `region` (string, required) — Russian region (federal subject) to list courts in (one of: "Республика Адыгея", "Алтайский край", "Республика Алтай", "Амурская область", "Архангельская область", "Астраханская область", "Республика Башкортостан", "Белгородская область", "Брянская область", "Республика Бурятия", "Организации центрального подчинения", "Чеченская Республика", "Челябинская область", "Чукотский автономный округ", "Чувашская Республика", "Республика Крым", "Республика Дагестан", "Донецкая Народная Республика", "Республика Ингушетия", "Иркутская область", "Ивановская область", "Еврейская автономная область", "Кабардино-Балкарская Республика", "Калининградская область", "Республика Калмыкия", "Калужская область", "Камчатский край", "Карачаево-Черкесская Республика", "Республика Карелия", "Кемеровская область", "Хабаровский край", "Республика Хакасия", "Ханты-Мансийский автономный округ", "Херсонская область", "Кировская область", "Республика Коми", "Костромская область", "Краснодарский край", "Красноярский край", "Курганская область", "Курская область", "Ленинградская область", "Липецкая область", "Луганская Народная Республика", "Магаданская область", "Республика Марий Эл", "Республика Мордовия", "Город Москва", "Московская область", "Мурманская область", "Ненецкий автономный округ", "Нижегородская область", "Республика Северная Осетия-Алания", "Новгородская область", "Новосибирская область", "Омская область", "Оренбургская область", "Орловская область", "Территории за пределами РФ", "Пензенская область", "Пермский край", "Приморский край", "Псковская область", "Ростовская область", "Рязанская область", "Город Санкт-Петербург", "Республика Саха (Якутия)", "Сахалинская область", "Самарская область", "Саратовская область", "Город Севастополь", "Смоленская область", "Ставропольский край", "Свердловская область", "Тамбовская область", "Республика Татарстан", "Томская область", "Тульская область", "Тверская область", "Тюменская область", "Республика Тыва", "Удмуртская Республика", "Ульяновская область", "Владимирская область", "Волгоградская область", "Вологодская область", "Воронежская область", "Ямало-Ненецкий автономный округ", "Ярославская область", "Забайкальский край", "Запорожская область")
- `name` (string, nullable) — Filter courts by name substring (minLength: 1)
- `count` (integer, required) — Max number of results to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "GaspravosudieCourt")
- `id` (string, required)
- `name` (string, nullable)
- `region` (string, nullable)
- `address` (string, nullable)
- `phone` (string, nullable)
- `email` (string, nullable)
- `website` (string, nullable)
- `subdomain` (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.