A Polish Law Text Database Scraped from LexLege, Article by Article

LexLege does the tedious part of Polish law: every code cut into addressable articles, every amendment dated, the next one flagged. We turn that into rows and tell you when ISAP must have the last word.

Plans from €169 a month · Free project assessment · Reply within 1 business day

CSV · Excel · JSON · XML · FTP · SFTP · Amazon S3 · Google Cloud

lexlege.pb.pl
A Polish Law Text Database Scraped from LexLege, Article by Article
lexlege.pb.plwhat you get
Typical fields for public registers
record_identity_namestatusregistered_ataddressdocument_url
Delivery

API, JSON feed or CSV, XLSX and JSON files

Schedule

One-time, monthly, weekly, daily or 3 times a day

Scoping a LexLege scraping project: acts, depth, refresh

  1. You send

    LexLege pages, filters, fields and a schedule

  2. We run the scrapers

    Built, monitored and repaired by our team

  3. You receive the data

    API, JSON feed or CSV, XLSX and JSON files

A scoping call settles three things. Which acts: the whole catalogue, the codes and tax statutes, or a watchlist of named laws. Which depth: current text by article, then per-article history with redlines, then the upcoming-changes calendar. Which refresh: a one-off corpus, a weekly pass or a daily diff driven by the change feed. Those answers set the price of a LexLege feed; page counts do not. On request each act also carries its ISAP entry and publication date.

The site sits behind Cloudflare, and anti-bot handling, proxy rotation and CAPTCHA solving are part of the service rather than a surcharge. We extract LexLege data only from pages open to any visitor, at polite rates: no login, no subscriber case law, no paid templates. Output comes as JSON or JSONL for retrieval pipelines, CSV or Parquet for analysts, or an API of your own, with source URL, base citation and collection time on every row.

LexLege data fields: act, article, paragraph, point and version

A LexLege scraper works on nested levels, and each level has an address of its own, so every row traces back to the page it came from.

  • ActShort title, full title such as Ustawa z dnia 26 czerwca 1974 r. - Kodeks pracy, the abbreviation the site uses (KP, KEA, pr. poczt.), the base citation in the form Dz.U.YYYY.0.POS with a t.j. suffix when it is a consolidated text, the slug, the archive flag and the PDF export. A table of contents lists every DZIAL, Rozdzial and Oddzial with its article range, and each division has a page of its own, as in /kodeks-pracy/rozdzial-iv-regulamin-pracy/260. Regulations open with a preamble quoting their legal basis, which ties an implementing act to its parent statute.
  • ArticleOne URL per unit: /kodeks-pracy/art-30, art-22-2 for article 22 with superscript 2, letter suffixes such as art-119zzl in Ordynacja podatkowa, and paragraf-1 for units of regulations and ethics codes. Each carries its number, an editorial title such as Rozwiazanie umowy o prace - a heading the official text does not have - and a body split into paragraphs (paragraf in the codes, ustep elsewhere) and numbered points, with repealed units kept as uchylony.
  • Cross-referencesCitations inside the text are live links to the cited article. Kodeks pracy holds 573 article units and 334 such links, 21 of them into other acts such as the trade union act, the sickness benefits act and GDPR.
  • Article versionHistoria jednostki lists the earlier states of an article back to 2011 with Stan prawny na, the amending act as Dz.U.2023.0.641.zm, Obowiazuje od and the full wording of that version, removed and inserted words marked separately - a redline, not just a date.
  • Act versionWersje aktu gives one row per version: date, status (Obowiazujacy stan prawny, Nadchodzace zmiany or Archiwalna), the amending Dz.U. position and the articles it touched. Ordynacja podatkowa alone runs to 152 versions, from 2011 to changes scheduled for 2027.

Around the text sit templates linked to each article and Prawo w praktyce commentary from the same branch of law. We map both to the article they sit on, with title and link.

LexLege data fields: act, article, paragraph, point and version
Polish consolidated acts on LexLege: change feed, archive flags, court rulings

Polish consolidated acts on LexLege: change feed, archive flags, court rulings

The change feed. Zmiany w prawie runs two tabs, Ostatnie zmiany and Najblizsze zmiany, both grouped by effective date, each act listed with the number of changes it takes that day and a link to its version table. A daily pass only has to re-read what moved.

Labels that mislead. Each act header prints Stan prawny aktualny na dzien with the current date, and each page title promises an aktualny tekst jednolity - on repealed acts, on ministerial regulations with no consolidated text and on EU regulations alike. Repeal shows only as the AKT ARCHIWALNY prefix in the title and slug. The base citation can trail the journal: at the end of September 2026 Kodeks pracy still named Dz.U. 2025 poz. 277, days after Dz.U. 2026 poz. 1245 appeared. An address for an article that does not exist still renders an article page with an empty body, so every unit is checked for real text before it enters a dataset.

Court rulings. The home page title promises orzeczenia, yet the open search returns articles, acts and documents only. Case-law lines sit in the paid LexLege SIP package, just as rulings once sat in the LexLege PRO tier of the old lexlege.pl.

Templates. The wzory pism library claims over 2,000 documents at a flat 25 zl each; we index titles, categories and types, never the paid files.

LexLege vs ISAP: a private reading layer over Dziennik Ustaw

Source
lexlege.pb.pl
Category
public registers
Delivery
API, JSON feed, CSV, XLSX
Plans
From €169 a month
Get a quote

Before buying LexLege data, know what LexLege is: a private legal information service, not an official publisher. It grew up in the ArsLege group of Prawomaniacy sp. z o.o., an Olsztyn company known for ArsLege law exam tests, and in 2026 it moved under Puls Biznesu, the Bonnier Business Polska daily. The old lexlege.pl address now forwards to lexlege.pb.pl, where the service calls itself a System Informacji Prawnej. The interface is Polish only.

The statute text is not LexLege's own work. Act pages name the Dziennik Ustaw position they are built on - for Kodeks pracy the official tekst jednolity Dz.U.2025.0.277.t.j. - and LexLege's editors fold every later amending act into that base. The site calls the result ujednolicone teksty, the Polish term for an unofficial consolidation, and that is exactly what it is. The first-hand record is ISAP, the Sejm Chancellery's register of acts from Dziennik Ustaw and Monitor Polski; anyone who needs the complete Polish legal acts database should start there. LexLege is a reading layer on top of it.

What the layer adds is structure. ISAP records each act with its text as published and its consolidations as PDF files; LexLege serves the wording in force article by article, every article at its own address, with an editorial title, a dated change log and a calendar of changes not yet in force. The catalogue is curated rather than complete: about 1,290 documents in its act list in September 2026 - roughly 590 statutes, 340 regulations and 300 repealed acts kept under an AKT ARCHIWALNY label. It also carries texts the official journals never print, such as the ethics codes of advocates, attorneys-at-law, notaries and bailiffs and the Warsaw exchange rulebooks for NewConnect and Catalyst.

25Developers
500+Customers
1.5BPages extracted
15,000+Hours saved for our clients

LexLege scraping plans and pricing

Airplane

€199one-time

Setup fee included

100,000
One-time
Up to 5 days
7 days

Helicopter

€169/ mo

Setup fee €499

250,000
Monthly
Up to 5 days
14 days

Glasses

€229/ mo

Setup fee €499

1,000,000
Weekly
Up to 5 days
30 days

Microscope popular

€349/ mo

Setup fee €499

2,000,000
Daily
Same day
60 days

DNA

€549/ mo

Setup fee €799

3,000,000
3 times daily
Same day
90 days

Delivery: CSV, JSON or XLSX files, our API or a JSON feed. MCP server on request.

Full plan details

What a LexLege scraper feeds: article search, model training, amendment alerts

Teams buy LexLege data for the shape of the law more than for the words, which the journal already publishes. Three uses keep coming back.

Retrieval that cites the article. Most questions about Polish law land on one provision - art. 30 of Kodeks pracy, art. 14 of the PIT act - and LexLege already cuts the law at that grain, with a stable address for every article and its paragraphs and points in order. A legal-tech assistant built on it can quote the unit it answers from, the editorial titles double as a subject index the statute lacks, and the in-text links give a citation graph without writing a parser.

Before-and-after pairs for models. The article history pairs each superseded wording with its replacement, the amending act and the in-force date, deletions and insertions marked. That is ready material for models that summarise a nowelizacja or answer as of a given day.

A calendar of what changes next. Payroll, tax and compliance teams care about the day a rule starts to apply. LexLege dates each change by entry into force and lists changes still in vacatio legis, so a watchlist of acts becomes a list of affected articles weeks ahead. It will not replace the official record: the catalogue covers a fraction of the journal, and final wording still gets checked against Dziennik Ustaw through ISAP.

Who runs the LexLege feed, and what stays out of it

ScrapeIt runs the job as a managed service. We design the collectors, schedule them, watch every run and repair them when LexLege renames a block, changes a URL pattern or moves host again, as it did in 2026. You receive files or an endpoint and keep no scraping engineers of your own.

We are not affiliated with LexLege, Puls Biznesu, Bonnier Business Polska, ArsLege or the Chancellery of the Sejm. Commentary bylines, author e-mail addresses and the questions readers send to the site's legal questions form stay out of every delivery: we collect law, not people.

FAQ

Still unsure? Write to info@scrapeit.io

Do you offer a LexLege API for Polish law text?

Yes. The ScrapeIt LexLege API returns acts, articles with their paragraphs and points, base citations, article versions and dated changes as JSON from an endpoint we host, refreshed on the schedule you set. The same data also comes as CSV or XLSX files or straight into your database.

Is LexLege an official source of Polish law?

No. Polish law binds in the wording published in the official journals, Dziennik Ustaw and Monitor Polski, and a consolidated text counts only once it is itself announced there. LexLege publishes unofficial consolidations, adds article titles of its own and can take days to switch to a newly announced tekst jednolity. That makes it excellent for reading, searching and tracking, but for a contract clause, a court filing or a compliance opinion the wording should be checked against the official publication, which ISAP links for every act.

Does LexLege include Polish court rulings data?

Not on the open site. Its page title mentions rulings, but public search covers only articles, acts and document templates, and the case-law lines LexLege does hold are part of the paid LexLege SIP package, behind a subscription we do not enter. Before the move to Puls Biznesu, rulings of the common and administrative courts also sat behind a paid PRO tier. For a Polish court rulings dataset, scope the courts' own portals instead: orzeczenia.ms.gov.pl for common courts and orzeczenia.nsa.gov.pl for administrative ones.

How current are the Polish consolidated acts on LexLege, and how often can a feed refresh?

For most major codes and the PIT, CIT and VAT acts the base citation matches the newest consolidated text in Dziennik Ustaw, and every change carries the date it enters into force, with upcoming changes listed in advance. Two caveats: a freshly announced tekst jednolity can take days to replace the base citation, and the date in the act header is simply today's date. A daily diff driven by the Zmiany w prawie feed keeps a dataset in step; weekly or monthly passes suit research corpora.

Is it legal to scrape LexLege data?

Yes. Acts, articles with their paragraphs and points, editorial titles, version tables and the calendar of upcoming changes are open to any visitor. We collect only publicly available data - everything a visitor can see on LexLege - and we collect it legally, keep every row traceable to its source and leave paid and subscriber content alone. We collect no personal data.

How it works

  1. 1

    Make a request

    You share your needs, expectations, and desired timeframe. We'll suggest the best solution based on your request and budget.

  2. 2

    We configure the crawlers

    Our specialists configure the crawlers and extract a sample dataset for your review before proceeding with the full-scale extraction.

  3. 3

    Collect and deliver

    Once you approve the sample, we launch the project and start full data collection. We gather, filter, and structure the data for easy use, delivering it on time in your preferred format.

  4. 4

    Maintain and support

    Our team manages ongoing processes, monitors website changes, and supports all data extraction cycles. We can also help integrate data into your systems or create dashboards to simplify analysis.

Request a quote

Tell us which sites, which fields and how often. A couple of lines is enough to start.

  • We reply within 1 business day
  • A sample dataset before the full run
  • We sign an NDA on request
  • Delivery by API, JSON feed or files
Which sites, which fields, how often. A couple of lines is enough.

This form is protected by Google reCAPTCHA, which loads when you start filling it in. If you prefer not to use it, email us at info@scrapeit.io. Privacy & Cookie Policy

We reply within 1 business day. No obligation.

LexLege data from €169/month. Free project assessment, reply within 1 business day.