/gaspravosudie/cases/search

POST /api/gaspravosudie/cases/search

Price: 50 credits

Search court cases in a specific Russian court of general jurisdiction by case number, unique case ID, party, judge or case-received date range, within a chosen type of proceedings.

How to use it

Search cases in one court. Provide court (subdomain from courts/search), case_type, count, and at least one of case_number, uid, party, judge, date_from/date_to (DD.MM.YYYY). Each result has case_id, case_uid, delo_id (use them or url for cases/cases/parties/cases/movement), url, case_number, received_date, category, plaintiff, defendant, judge.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• court string required — Court subdomain (resolve via courts/search) (examples: "oktiabrsky.svd.sudrf.ru")
• case_type string required — Type of court proceedings (one of: "Гражданские дела", "Административные дела (КАС)", "Уголовные дела", "Дела об административных правонарушениях")
• case_number string nullable — Case number
• uid string nullable — Case unique ID (UID)
• party string nullable — Party surname / name
• judge string nullable — Judge surname
• date_from string nullable — Earliest case-received date (DD.MM.YYYY)
• date_to string nullable — Latest case-received date (DD.MM.YYYY)
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "GaspravosudieCaseSearchResult")
• case_id string required
• case_uid string required
• delo_id string required
• url string required
• case_number string nullable
• received_date string nullable
• category string nullable
• plaintiff string nullable
• defendant string nullable
• judge string nullable
• decision_date string nullable
• result 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 — The entity was not found, or a precondition failed 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.