/gaspravosudie/acts

POST /api/gaspravosudie/acts

Price: 1 credit

Get a single judicial act of a Russian court of general jurisdiction by its identifier: full act text, act type, case number, unique case ID (UID), date, court, region, judge and the parties (plaintiffs, defendants, third parties).

How to use it

Fetch a single judicial act by its id (or full act URL). Returns one item with id, url, title, act_type, case_number, uid, date, court, court_url, region, case_type, judge, plaintiffs, defendants, third_parties, judges and the full act text.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• act string required — Judicial act identifier or full act URL (examples: "0Y7b4d4xbfK", "https://sudact.ru/regular/doc/0Y7b4d4xbfK/"; minLength: 1)

Response

• @type string (default: "GaspravosudieAct")
• id string required
• url string required
• act_type string nullable
• case_number string nullable
• uid string nullable
• date string nullable
• court string nullable
• court_url string nullable
• region string nullable
• case_type string nullable
• judge string nullable
• plaintiffs array (default: [])
• defendants array (default: [])
• third_parties array (default: [])
• judges array (default: [])
  • @type string (default: "GaspravosudieActParty")
  • name string required
  • role string nullable
  • url string nullable
• text string nullable

Errors

• 422 — 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 — Act not found (no judicial act matches the given identifier) 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.

Response 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.