/gaspravosudie/cases/movement

POST /api/gaspravosudie/cases/movement

Price: 10 credits

Get the movement timeline of a court case from a Russian court of general jurisdiction: each procedural event with its date, time, location, result, basis and publication date.

How to use it

List the movement (procedural timeline) of a case. Provide either url (full case-card URL) or all of court, case_id, case_uid and delo_id. Each result has event, date, time, place, result, basis, note, published_date.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• url string nullable — Full case-card URL (examples: "https://oktiabrsky--svd.sudrf.ru/modules.php?name=sud_delo&srv_num=1&name_op=case&case_id=574341722&case_uid=b86ef5ac-dc0c-4bfe-8b84-0d0e934b7f6e&delo_id=1540005")
• court string nullable — Court subdomain (e.g. oktiabrsky.svd.sudrf.ru) (examples: "oktiabrsky.svd.sudrf.ru")
• case_id string nullable — Internal case id
• case_uid string nullable — Case UUID
• delo_id string nullable — Case-index (production type) id, e.g. 1540005

Response

• @type string (default: "GaspravosudieCaseMovement")
• event string required
• date string nullable
• time string nullable
• place string nullable
• result string nullable
• basis string nullable
• note string nullable
• published_date 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 — Case not found (no case 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.