# /rusprofile/companies/arbitrations

`POST /api/rusprofile/companies/arbitrations`

Price: 10 credits

Get arbitration (commercial-court) cases for a Russian company by INN, OGRN or internal id. Each case lists the case number and date, status, outcome, category and type, claim amount, plaintiffs, defendants and third parties (with their Rusprofile ids), court instances with events, and the KAD (kad.arbitr.ru) case link.

## How to use it

Fetch arbitration cases for a Russian legal entity by INN, OGRN, internal Rusprofile id or company URL. Provide company and count. Each case has number, date (YYYY-MM-DD), status, outcome, category, type, amount (RUB), plaintiffs, defendants, third_parties (each with name and id), instances (court stages with date and event) and kad_url. This data is unique to Rusprofile among the Russian registry sources.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `company` (string, required) — Company INN (10 digits), OGRN (13 digits), internal Rusprofile id or a full company URL (examples: "7707083893", "2835629", "https://www.rusprofile.ru/id/2835629"; minLength: 1)
- `count` (integer, required) — Max number of arbitration cases to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "RusprofileArbitrationCase")
- `number` (string, nullable)
- `date` (string, nullable)
- `status` (string, nullable)
- `outcome` (string, nullable)
- `category` (string, nullable)
- `type` (string, nullable)
- `amount` (integer, nullable)
- `plaintiffs` (array) (default: [])
  - `@type` (string) (default: "RusprofileCaseParty")
  - `name` (string, nullable)
  - `id` (string, nullable)
- `defendants` (array) (default: [])
  - `@type` (string) (default: "RusprofileCaseParty")
  - `name` (string, nullable)
  - `id` (string, nullable)
- `third_parties` (array) (default: [])
  - `@type` (string) (default: "RusprofileCaseParty")
  - `name` (string, nullable)
  - `id` (string, nullable)
- `instances` (array) (default: [])
  - `@type` (string) (default: "RusprofileCaseInstance")
  - `name` (string, nullable)
  - `date` (string, nullable)
  - `event` (string, nullable)
- `kad_url` (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

Company not found (well-formed INN/OGRN but no matching record in the registry)

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.