Read a provision or paragraphs
read_paragraphsSign-in required: call connect(email) and connect_verify first (free, one email) unless this connection is already signed in. Read a document by its own structure: give a pinpoint (straipsnis) like '6.38' for one article, or from_unit and count to page through it. On a ruling (nutartis / sprendimas), pass ruling_part=disposition to read only the operative order (rezoliucinė dalis). Never by character offset (read_source_text reads the publisher's text that way, without our structure). document_id is required and comes from a result: a search hit's id (an article id with # opens at that article) or document.id; a case number or an act number is not an id (find it with search_practice / search_law first). Page size is count; there is no limit or max_chars here. paragraphs contain the served text; inspect its version/wording qualifications before calling it current law. on_date requests separate wording_on_date, whose held/composed/missing evidence must support any historical claim. A # unit or pinpoint overrides from_unit. For whole-document paging, continue an unfiltered read as shown below. ECHR cases (coe.hudoc:) have no paragraphs here: the answer is the case card and its HUDOC link. Example arguments: {"document_id": "<document_id from search result>", "pinpoint": "6.217", "count": 1, "on_date": "2024-01-15"}. Replace the first bracketed document_id with the id returned by your search. To continue an unfiltered read, use its response document_id without a # fragment, set from_unit to its next_from_unit, omit pinpoint/article, and keep other filters. A next_from_unit from a pinpoint-filtered read is not a whole-document offset. Continuation arguments: {"document_id": "<document_id from previous read>", "from_unit": 14, "count": 3, "on_date": "2024-01-15"}.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Which language version to read, as a two-letter code (`lt`, `en`, `fr`), for a document held in several languages; `<id>@en` in `document_id` does the same. Omit for the default version: Lithuanian where held, else the source language. Pinpoints are the same in every language; the answer names the language served and the others held. | |
| count | No | How many paragraphs to return, default 5. With `pinpoint`/`article` and no count you get that provision's own paragraphs; with a count, the read opens at the provision and reads on in document order (`pinpoint='31 p.', count=3` gives paragraphs 31-33). The Civil Code runs to 1.7 million characters, so read in pages rather than asking for everything. | |
| voice | No | On a ruling only: return only the paragraphs in this voice - `court` (the court alone speaking, including its restatements of earlier rulings; `court_own` without them; `court_interpretation` its interpretation only), `party` (a party's argument or the question its appeal raises), `lower_court`, `institution`, `opinion`, or one voice name. Every paragraph of a ruling carries `voice` either way; a paragraph with more than one speaker is `mixed`, with each fragment's voice. | |
| article | No | Jump to an article by its number alone: `57`, `6.217`. Same effect as `pinpoint` with less typing — pass one or the other, not both naming different articles. | |
| on_date | No | On an act's article: `YYYY-MM-DD` requests separate `wording_on_date`, with its edition window, link and held/composed/missing qualification. Passing the date does not make `paragraphs` historical: they contain the text served by this read. Inspect `version` and `wording` qualifications before treating that text as current law. Use the separate dated result only to the extent its evidence supports it. | |
| section | No | On a ruling only: the numbered section(s) the court prints - `IV` for section IV, `IV+` (or `nuo IV`) for it and every later one. Combines with ruling_part: ruling_part=`reasoning`, section=`IV+` reads only the court's reasoning from section IV on, in one call. | |
| session | No | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key. | |
| pinpoint | No | Jump to a location by name, as a lawyer writes it: `6.217 straipsnis`, `13 straipsnis. 2 dalis`. Omit when the id already names the place. | |
| from_unit | No | One-based position for a read without `pinpoint`/`article`, using the response's `document_id` without a `#` fragment. A `#` unit or pinpoint overrides it. Continue an unfiltered read with `next_from_unit`; that value from a pinpoint-filtered read is not a whole-document offset. There is no cursor. | |
| document_id | Yes | What to read: the `id` of a search hit - an article id (containing `#`) opens at that article and reads on - or the whole document's id to start at the top. | |
| ruling_part | No | On a ruling only: return paragraphs from one section — `recital` (case history and parties' arguments under nustatė), `reasoning` (konstatuoja) or `disposition` (nutaria — the operative order). Omit for statutes. | |
| jurisdiction | No | Which jurisdiction the id belongs to (`LT`). Omit for the account's own. | |
| guidance_limit | No | How many explanations (institutional guidance linked to the article read) come with it: 0 for none, at most 30; omit for the default (10). `guidance.total` still counts every one linked. |