NL Jurisprudentie Monitor per Rechtsgebied 🇳🇱

Monitor Dutch court rulings (jurisprudentie) by legal area and court instance — with automatic change detection and landmark signals for Hoge Raad (Supreme Court), Raad van State and Centrale Raad van Beroep decisions.

data.rechtspraak.nl publishes thousands of rulings every month across dozens of legal areas and court levels. Finding the ones relevant to your practice or research currently means searching through a flat, unfiltered list. This actor turns that open data feed into a structured, incremental stream grouped by rechtsgebied and instantie, so you can monitor new decisions in the areas that matter to you.

Who is this for?

• Law firms & legal departments tracking new rulings in specific practice areas (e.g. arbeidsrecht, bestuursrecht)
• Legal tech & AI platforms needing clean, structured ruling data for RAG or knowledge-base updates
• Compliance teams monitoring regulatory shifts in specific jurisdictions or court levels
• Researchers & journalists tracking Hoge Raad (Supreme Court) landmark decisions
• Government & policy analysts following developments in administrative or tax law
• AI agents — flat JSON output, MCP-ready, ideal for agentic legal research workflows

When should an AI agent use this?

• "Show me new arbeidsrecht rulings from the Rechtbank since yesterday."
• "Which Hoge Raad (Supreme Court) decisions were published this week in civiel recht?"
• "Has there been a new bestuursrecht ruling on vreemdelingenrecht from the Gerechtshof?"
• "List all new rulings in my subscribed legal areas since the last run."
• "Give me the latest Hoge Raad landmark decisions with full metadata."
• "Monitor for new tax law (belastingrecht) rulings and alert me when they appear."

What this Actor does

• Incremental monitoring — only returns rulings modified since the previous run, so you get new and changed decisions without duplicates
• Legal area filtering — client-side filtering by rechtsgebied (the official API does not support server-side area filtering)
• Court instance filtering — filter by Hoge Raad, Gerechtshof, or Rechtbank
• Landmark signal — rulings from Hoge Raad (Supreme Court), Raad van State (highest administrative court) and Centrale Raad van Beroep (highest court for social security/civil service law) are flagged isLandmark: true because these highest-instance colleges carry binding weight as precedent within their legal domain
• Two-step fetch architecture — first fetches a search result list (ECLI identifiers), then enriches each ruling with content (legal area, court, summary, links)
• Flat, structured output — one JSON object per ruling, grouped by legal area and court, ready for datasets, webhooks, or MCP tools

Input options

Field	Description	Example
rechtsgebieden	Filter by legal area. Leave empty to include all.	["Civiel recht", "Bestuursrecht"]
instantieTypes	Filter by court instance level	["Hoge Raad", "Gerechtshof", "Rechtbank"]
maxResults	Maximum number of rulings to return (1-500)	100
alleenNieuweSindsVorigeRun	Only return rulings modified since the previous run	true
trackVolumeTrend	Compare the number of rulings per legal area against the previous run	false
haalVolledigeTekstOp	Extract the full ruling text (no extra API call — already in the fetched content response)	false

Output

Each result is one court ruling, enriched with metadata from the content endpoint:

{
  "ecli": "ECLI:NL:HR:2023:1234",
  "titel": "ECLI:NL:HR:2023:1234, Hoge Raad, 15-03-2023, Uitspraak over arbeidsrecht",
  "instantie": "Hoge Raad",
  "datum": "2023-03-15",
  "rechtsgebied": "Civielrecht",
  "rechtsgebiedUri": "http://psi.rechtspraak.nl/rechtsgebied#civielRecht",
  "samenvatting": "Samenvatting van de uitspraak...",
  "urlHtml": "https://zoek.rechtspraak.nl/uitspraken?id=ECLI:NL:HR:2023:1234",
  "urlContentXml": "https://data.rechtspraak.nl/uitspraken/content?id=ECLI:NL:HR:2023:1234",
  "isNieuweUitspraakSindsVorigeRun": true,
  "isLandmark": true,
  "volledigeTekst": null
}

• rechtsgebied is normalized from the official PSI taxonomy (free-text in the source is mapped to a canonical label)
• isLandmark is true for Hoge Raad (Supreme Court), Raad van State and Centrale Raad van Beroep rulings — these highest-instance colleges carry the most weight as binding precedent within their legal domain
• isNieuweUitspraakSindsVorigeRun is true when alleenNieuweSindsVorigeRun is enabled and the ruling was modified since the previous run
• volledigeTekst is null unless haalVolledigeTekstOp is enabled and text was actually found

Full ruling text (haalVolledigeTekstOp, optional, separately charged)

With haalVolledigeTekstOp: true, volledigeTekst is filled with the full text of the ruling, extracted from the same content response already fetched for the metadata — no third API call, since the response that provides instantie/rechtsgebied/samenvatting already contains the full <uitspraak> (or <conclusie> for advocate-general opinions) body. Charged as volledige-tekst-record, only when text is actually extracted (a ruling type without that element, or a parse miss, gets volledigeTekst: null and no charge).

Volume trend per legal area (trackVolumeTrend, optional, separately charged)

With trackVolumeTrend: true, the actor counts how many rulings were delivered per rechtsgebied this run and compares that against the previous run's count (stored in its key-value store). One extra dataset record per legal area seen this run or last run:

{
  "type": "volumetrend-signaal",
  "rechtsgebied": "Strafrecht",
  "huidigAantal": 12,
  "vorigAantal": 10,
  "percentageVerandering": 20,
  "periodeVanaf": "2026-07-09",
  "periodeTot": "2026-07-16"
}

percentageVerandering is null when the legal area wasn't seen in the previous run (no known baseline) or the previous count was 0 (division by zero gives no meaningful percentage). Charged as volumetrend-signaal, only for legal areas where a percentage was actually computable.

Use cases

Daily monitoring for a legal practice, Hoge Raad landmarks only:

{
  "rechtsgebieden": ["Civiel recht", "Bestuursrecht"],
  "instantieTypes": ["Hoge Raad"],
  "maxResults": 50,
  "alleenNieuweSindsVorigeRun": true
}

Full scan of arbeidsrecht rulings across all courts, last 90 days:

{
  "rechtsgebieden": ["Arbeidsrecht"],
  "instantieTypes": ["Hoge Raad", "Gerechtshof", "Rechtbank"],
  "maxResults": 200,
  "alleenNieuweSindsVorigeRun": false
}

Track tax law changes from the Gerechtshof only:

{
  "rechtsgebieden": ["Belastingrecht"],
  "instantieTypes": ["Gerechtshof"],
  "maxResults": 100,
  "alleenNieuweSindsVorigeRun": true
}

Scheduling & integrations

• Schedules — run daily or weekly and get only new/changed rulings since the last run
• Integrations — push results to Google Sheets, Slack, Zapier, Make, or any webhook
• API — fetch the dataset as JSON, CSV or Excel from your own code
• MCP — expose this actor as a tool for AI agents (Claude, Cursor, and other MCP clients)

Data source & legality

This actor uses the official open data API of the Dutch judiciary (data.rechtspraak.nl), the same source behind zoek.rechtspraak.nl.

• ✅ No scraping — official Atom feed and structured XML content endpoint, no login required
• ✅ Court rulings are public documents intended for open access; no personal data involved
• ⚠️ This actor is a monitoring/search tool, not legal advice. Always consult the official ruling (urlHtml) for legally binding interpretation.

Pricing

Pay-per-event: you only pay for rulings actually delivered, plus a small extra charge for each ruling flagged as new since the last run (incremental mode).

Event	Price	Description
apify-actor-start	$0.00005	Apify default
uitspraak-result	$0.003	Each ruling delivered to your dataset
rechtsgebied-alert	$0.008	Each new ruling in incremental mode (premium signal for change detection)
volledige-tekst-record	$0.015	Per ruling, only with haalVolledigeTekstOp enabled and text actually extracted
volumetrend-signaal	$0.01	Per legal area, only with trackVolumeTrend enabled and a previous count actually known

FAQ

Why two API calls per ruling? The official API's search endpoint does not support filtering by legal area (rechtsgebied). The actor first fetches a list of ECLIs matching your date filter, then enriches each one individually to extract the legal area and court instance.

What's the rate limit? The source allows roughly 10 requests per second. The actor enforces a 100ms delay between content fetches to stay within limits.

Why does maxResults max out at 500? Each result requires an extra content fetch. Higher limits would make runs very slow and risk hitting rate limits. Use scheduled incremental runs for ongoing monitoring instead.

Is isLandmark only for Hoge Raad? No — isLandmark is true for Hoge Raad (Supreme Court), Raad van State (highest administrative court) and Centrale Raad van Beroep (highest court for social security and civil service law) rulings. These are the highest-instance colleges with binding precedent value within their respective legal domains. Gerechtshof and Rechtbank rulings are important but not formally "landmark" in the same sense.

How does incremental mode work? On the first run (no stored baseline yet), the actor looks back 30 days via modified=<30 days ago> so it doesn't come back empty. On subsequent runs, it uses modified=<lastRunDate> to fetch only rulings changed since then, and stores today's date as the new baseline. Each ruling is flagged isNieuweUitspraakSindsVorigeRun: true.

What happens when alleenNieuweSindsVorigeRun is disabled? The actor still bounds the scan to the last 90 days via modified — it does not crawl the entire rechtspraak.nl archive from its oldest entry onward. Rulings are not flagged isNieuweUitspraakSindsVorigeRun in this mode.

Related Actors

Also by this developer — Dutch/EU public-data actors that pair well with this one:

• NL CAO Wijzigingen Database — same official-publication → structured-feed pattern, applied to Dutch collective labour agreement changes.
• NL & EU Government Tenders Scraper — structured feed from government procurement tenders, useful for legal teams tracking public contract opportunities.
• NL Emissiezones Monitor — Dutch environmental zone monitoring with change detection, same incremental alerting pattern.

---

Zoekwoorden: rechtspraak monitor, jurisprudentie per rechtsgebied, Hoge Raad uitspraken, Nederlandse rechtspraak, rechtsgebied alerts, uitspraken feed, rechtbank monitoring, civiel recht, bestuursrecht, strafrecht, arbeidsrecht, belastingrecht, vreemdelingenrecht, legal tech NL, open data rechtspraak.

Keywords

rechtspraak, jurisprudentie, uitspraken, Hoge Raad, gerechtshof, rechtbank, rechtsgebied, legal monitoring, netherlands, open data, precedent, legal tech, ECLI, rechtspraak.nl, civiel recht, bestuursrecht, strafrecht, arbeidsrecht, belastingrecht, vreemdelingenrecht

Changelog

0.2.0 - Full text extraction & volume trend

• Added haalVolledigeTekstOp — extracts the full ruling text (volledigeTekst) from the same content response already fetched for the metadata, no extra API call. New volledige-tekst-record event ($0.015), only charged when text is actually found.
• Added trackVolumeTrend — compares the number of rulings delivered per legal area against the previous run via the key-value store. New volumetrend-signaal event ($0.01), only charged when a previous count is actually known for that legal area.

0.1.2 - Enhancement

• Landmark signal extended: isLandmark now also flags Raad van State and Centrale Raad van Beroep rulings, next to Hoge Raad, since these are also highest-instance colleges with precedent value in their legal domain
• Legal area normalization extended: normaliseerRechtsgebied() now also recognizes Personen- en familierecht, Arbeidsrecht, Insolventierecht, Verbintenissenrecht, Ambtenarenrecht, Europees recht and Internationaal publiekrecht, reducing the number of rulings that fall through to unmapped free text

0.1.1 - Bugfix

• Fixed incremental mode never seeing the previous run's lastRunDate: the actor was reading/writing to Apify's per-Run default key-value store, which is not shared between separate runs. Now uses a named, persistent key-value store.

0.1.0 - Initial release

• Incremental ruling monitor with two-step fetch architecture (search + content enrichment)
• Filtering by legal area (client-side) and court instance (Hoge Raad / Gerechtshof / Rechtbank)
• Landmark signal for Hoge Raad rulings (isLandmark: true)
• Key-value store for incremental mode (alleenNieuweSindsVorigeRun)
• PPE pricing: uitspraak-result @ $0.003, rechtsgebied-alert @ $0.008