Docs / REST API
GET /v1/act
Resolve an act by its requisites (date + number) → internal code
Lawyers cite acts by requisites, not by code: 'Plenum ruling of 28.06.2012 No. 17'. Key is strict: type + number + date. A bare number returns ambiguous:true with the list — an act number alone is NOT an identifier (843 documents share number '253' in the RF gazette).
Endpoint
GET https://api.lexatlas.creatora.app/v1/act
Parameters
| Name | In | Required | Type | Description |
|---|---|---|---|---|
| jur | query | yes | string | jurisdiction, e.g. ru |
| date | query | no | string | act date YYYY-MM-DD |
| no | query | no | string | act number |
| kind | query | no | string | act kind filter, e.g. court_practice |
Example
curl -H "X-API-Key: lxa_YOUR_KEY" \
"https://api.lexatlas.creatora.app/v1/act?jur=ru"Responses and error codes
| Status | Meaning | Schema |
|---|---|---|
| 200 | matching acts with codes, titles and where they were found | object |
| 400 | bad request — see error_code (missing_parameter, invalid_parameter, invalid_body, invalid_cursor, empty_batch, batch_too_large, unsupported) | Error |
| 401 | missing/invalid API key (when auth is enabled) — error_code=unauthorized | Error |
| 413 | body too large — error_code=payload_too_large | Error |
| 429 | rate limit exceeded (per-key, per-minute window) — error_code=rate_limited | Error |
Errors use one envelope everywhere: error, error_code, hint, http_status. The full list of codes is served by GET /v1/errors.