NL Wet- en Regelgevingtracker per Sector — Dutch Legislation Sector Tracker 🇳🇱⚖️

Get new and changed Dutch legislation — wetten, AMvB's (Algemene Maatregelen van Bestuur), and ministeriële regelingen — automatically classified per business sector, delivered as a structured feed for compliance teams.

Dutch compliance departments (banks, insurers, healthcare providers) have a legal obligation to track legislative changes relevant to their sector. This actor turns the official KOOP/Staatsblad publication stream into a filtered, sector-tagged feed, so you know the moment a law relevant to your industry changes.

When should an AI agent use this?

• "Which new laws or AMvBs were published in the Netherlands affecting the healthcare sector this month?"
• "Monitor Dutch legislation for anything relevant to financial services (Wft, DNB, AFM)."
• "Has any new energy-sector regulation (Energiewet, Elektriciteitswet) been published since last week?" (using incremental mode)
• "Give me a nationwide feed of new Wet/AMvB publications, only new items since yesterday."
• "Classify these legislative publications by sector using my own keyword list."

What this Actor does

• Searches the official KOOP SRU API (repository.overheid.nl/sru, the source behind officielebekendmakingen.nl / Staatsblad) for legislation of the requested document type(s)
• Supports Wet, AMvB, Ministeriële regeling, Rijkswet, Klein Koninklijk Besluit, circulaire and beleidsregel as filterable document types
• Classifies each publication into one or more sectors by matching keywords against its title — a configurable, transparent alternative to a native "sector" field (which does not exist in the source data)
• Returns sectoren: null for publications that do not match any configured sector — this is a normal, useful result (not every law is sector-specific), never an error
• Classifies each publication's wijzigingType (nieuwe_regeling / wijziging / intrekking / overig) based on the fixed Staatsblad title phrasing, so compliance teams can distinguish a brand-new law from a routine amendment at a glance
• Supports incremental mode: only new/changed publications since the previous run
• Optional volledigeTekstClassificatie fallback: when the title has no sector match, fetch and classify the full text instead — catches sector-relevant content hidden behind a generic title, and fills samenvattingSnippet from the full text as a bonus

Who is this for?

• Compliance departments (banks, insurers, healthcare providers) — required by law to track legislative changes affecting their sector (Wft-vergunninghouders, Wtza-zorgaanbieders, etc.)
• Legal & regulatory affairs teams — early visibility into new/changed legislation before it hits commercial legal-information services
• AI agents / RAG pipelines — a structured, machine-readable feed of Dutch legislation to ground legal research or compliance-monitoring assistants
• Consultancies & law firms — a base data feed for building sector-specific legislative alerts for clients

Input

Field	Type	Description
documentTypes	array	Which KOOP document types to fetch. Default ["Wet", "AMvB"]. Options: Wet, AMvB, Ministeriële regeling, Rijkswet, Klein Koninklijk Besluit, circulaire, beleidsregel.
sectorKeywords	object	Map of sector name → list of keywords, matched case-insensitively against the title. Leave empty (default) to use the built-in set: zorg, bouw, financiële sector, arbeidsrecht, energie, mobiliteit. Provide your own object to fully override the defaults.
publishedAfter	string	Only publications modified on/after this date (YYYY-MM-DD).
maxResults	integer	Maximum number of records to return (1-10000). Default 200.
incrementalMode	boolean	Only fetch publications newer than the previous run. Default false.
volledigeTekstClassificatie	boolean	When the title has no sector match, fetch and classify the full text instead (1 extra HTTP request per unmatched record). Also fills samenvattingSnippet. Default false.
trackSectorTrend	boolean	Compare the number of sector-match-alerts per sector this run against the previous run. Default false.

Output

{
  "id": "stb-2026-116",
  "titel": "Besluit van 20 mei 2026 tot wijziging van het Uitvoeringsbesluit kinderbijslagvoorziening BES in verband met de invoering van de dubbele kinderbijslag bij intensieve zorg BES",
  "documentType": "AMvB",
  "wijzigingType": "wijziging",
  "sectoren": ["zorg"],
  "publicatiedatum": "2026-05-27",
  "publicatienummer": "116",
  "bron": "Staatsblad",
  "volledigeTekstUrl": "https://repository.overheid.nl/frbr/officielepublicaties/stb/2026/stb-2026-116/1/html/stb-2026-116.html",
  "samenvattingSnippet": null,
  "sectorMatchViaVolledigeTekst": false
}

sectorMatchViaVolledigeTekst is true only when volledigeTekstClassificatie is enabled and the sector match was found in the full text after the title itself had no match — this is the signal for the extra sector-match-verrijkt charge, and it also means samenvattingSnippet got filled from the full text.

sectoren is often null — most legislation does not match a configured sector keyword. This is a valid, expected result, not a failure to classify.

wijzigingType is "overig" when the title doesn't match a known Staatsblad phrasing — this is an honest fallback, not a guess. It never invents a nieuwe_regeling/wijziging/intrekking label without a matching, live-confirmed title pattern.

Same-day duplicate protection (incrementalMode)

dt.modified filtering only has day-level granularity, so running the actor a second time on the same day (e.g. a morning + evening schedule) used to re-deliver — and re-charge for — the same records. The actor now also tracks which record IDs were already delivered today (in the key-value store) and skips them on a second run the same day, at no charge. No behavior change across different days.

Run summary (free extra dataset record)

Whenever at least one record is delivered, one extra dataset item with "type": "RUN_SUMMARY" is pushed at the end of the run — no extra charge: total records, a breakdown per sector and per wijzigingType, and how many sector matches were found only via the full-text fallback.

Sector trend between runs (trackSectorTrend, optional, separately charged)

With trackSectorTrend: true, the actor counts how many sector-match-alerts occurred per sector this run and compares that against the previous run's count (stored in its key-value store). One extra dataset record per sector seen this run or last run:

{
  "type": "sector-trend-signaal",
  "sector": "zorg",
  "huidigAantal": 12,
  "vorigAantal": 10,
  "percentageVerandering": 20
}

percentageVerandering is null when the sector 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 sector-trend-signaal, only for sectors where a percentage was actually computable.

Use cases

Daily nationwide legislation feed, incremental:

{ "incrementalMode": true }

Monitor only healthcare and financial-sector legislation, using the built-in defaults:

{
  "documentTypes": ["Wet", "AMvB", "Ministeriële regeling"],
  "publishedAfter": "2026-01-01"
}

Then filter the output dataset on sectoren containing "zorg" or "financiële sector".

Use a fully custom sector keyword set:

{
  "sectorKeywords": {
    "cybersecurity": ["cyberbeveiliging", "nis2", "digitale weerbaarheid"],
    "privacy": ["avg", "gegevensbescherming", "persoonsgegevens"]
  }
}

Pricing

This Actor uses Apify's Pay-Per-Event (PPE) pricing model.

• Actor Start: $0.00005 (Apify default)
• regelgeving-record: $0.003 per delivered record (base data)
• sector-match-alert: $0.008 extra, only when a record matches at least one configured sector
• sector-match-verrijkt: $0.006 extra on top of sector-match-alert, only with volledigeTekstClassificatie enabled and only when the match was found via the full-text fallback (title itself had no match)
• sector-trend-signaal: $0.008 per sector, only with trackSectorTrend enabled and a previous count actually known for that sector

Legal

This actor uses the official public SRU API of the Dutch government (KOOP / repository.overheid.nl, the same source behind officielebekendmakingen.nl / Staatsblad) — the same source used by NL CAO-wijzigingen Database. No scraping of protected websites, no login, no terms-of-service conflicts.

• Wetten, AMvB's and ministeriële regelingen are, by definition, generally binding rules — not decisions about individual natural persons. This is a lower AVG/GDPR-risk data source than most other actors in this portfolio.
• Sector classification is a best-effort keyword match on the publication title, not legal advice. It does not replace a qualified legal/compliance review of whether a specific law applies to your organization.

FAQ

Q: How fresh is the data? A: Publications appear in the feed the same day KOOP publishes them.

Q: Why is sectoren often null? A: Most Dutch legislation does not concern any of the configured sectors — this is expected, not a bug.

Q: Can I add my own sectors? A: Yes — set sectorKeywords to your own object; it fully replaces the built-in defaults.

Q: How do I get only new/changed legislation? A: Enable incrementalMode and schedule the actor; it remembers the date of the previous run.

Q: Does this include jurisprudence (court rulings)? A: No — this actor covers wet- en regelgeving (legislation) only, not rechtspraak (case law).

Q: What's the difference between wijzigingType and sectoren? A: sectoren tells you which industry a publication is about; wijzigingType tells you what kind of legal event it is (brand-new regulation vs. an amendment to an existing one vs. a repeal). Use both together, e.g. filter on sectoren containing "zorg" AND wijzigingType == "nieuwe_regeling" to spot entirely new healthcare legislation specifically.

Related Actors

• NL CAO-wijzigingen Database — tracks collective labour agreement (CAO) changes on the same official KOOP SRU source, for the arbeidsrecht/HR angle specifically.

---

Zoekwoorden: wetgeving monitor, regelgeving tracker Nederland, compliance monitoring wet- en regelgeving, Staatsblad wijzigingen, AMvB monitor, wetswijzigingen per sector, regulatory tracker Netherlands.

Keywords

wetgeving, regelgeving, compliance, staatsblad, wet, amvb, ministeriele-regeling, sector, netherlands, legal-monitoring

Changelog

0.4.0 - Sector trend between runs

• Added trackSectorTrend (opt-in) — compares the number of sector-match-alerts per sector against the previous run via the key-value store, exposed as a sector-trend-signaal dataset record per sector. New sector-trend-signaal event ($0.008), only charged when a previous count is actually known for that sector.

0.3.2 - Bugfix

• Fixed same-day duplicate charges in incrementalMode: a second run on the same day (dt.modified only has day-level granularity) no longer re-delivers and re-charges the same records. Delivered IDs for the current day are now tracked in the key-value store.
• Added a free RUN_SUMMARY dataset record at the end of each run (totals per sector/wijzigingType, and how many matches came via the full-text fallback). No pricing change.

0.3.1 - Bugfix

• Fixed incrementalMode 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. A new baseline will be captured on the next run.

0.3.0

• Added volledigeTekstClassificatie (default false): when a title has no sector match, optionally fetch and classify the full text instead — catches sector-relevant content hidden behind a generic title, same patroon as nl-cao-wijzigingen-database. Fills samenvattingSnippet from the full text as a side effect. New sectorMatchViaVolledigeTekst field flags matches found this way. New charged event sector-match-verrijkt ($0.006, on top of sector-match-alert), confirmed by the user (2026-07-14).

0.2.0

• Added wijzigingType classification (nieuwe_regeling/wijziging/intrekking/overig) based on fixed Staatsblad title phrasing, so a brand-new law can be told apart from a routine amendment without a full-text fetch. No pricing change — enrichment of the existing per-record output.

0.1.0

• Initial release. Fetch Dutch legislation (Wet/AMvB/Ministeriële regeling/etc.) via the official KOOP SRU API, classify per sector via configurable keyword matching, incremental mode.