National law·Netherlands·Nederland

§ NL — National Law Desk

Dutch law,
as an API.

Dutch legislation and case law from wetten.overheid.nl and Rechtspraak open data, as structured JSON next to EUR-Lex — same API key, same credit pool.

In short

LexAPI is a REST API that serves the Netherlands’ consolidated acts and regulations in force (Basiswettenbestand) and published court decisions from de Rechtspraak as structured JSON, next to EU law from EUR-Lex: one API key, one credit pool and one document shape for every country. The data comes from wetten.overheid.nl and Rechtspraak open data, synced daily, with the source’s attribution on every response.

§ I — Coverage
Legislation

Consolidated regelingen (acts and regulations) in force (Basiswettenbestand, wetten.overheid.nl).

Case law

Published decisions with full text, and the opinions (conclusies) published with them, mostly from the Parket bij de Hoge Raad (de Rechtspraak open data).

§ II — Why LexAPI

The source is free. Here is what LexAPI adds.

KOOP publishes the consolidated regulations on wetten.overheid.nl with an SRU search service, and de Rechtspraak runs an open-data API for its published decisions. The Basiswettenbestand and Rechtspraak open data are both public domain (CC0). Consolidated texts are not the authentic Staatsblad / Staatscourant publication. LexAPI reads that data; it does not replace the source. It saves you building and running a pipeline per source, and puts the Netherlands next to EU law and the other countries in one schema.

  1. 01 · One document shape for every country

    The Netherlands answers with the same fields as every other country: documentKind (act or decision), title, ecli, eli, dateOfDocument, inForce / validTo, and court and case numbers for decisions. A field the source lacks is null, never missing.

  2. 02 · EU and national law on one key

    EUR-Lex legislation, CJEU case law and the Netherlands’ law come from the same API, with one key and one credit pool. One integration covers both.

  3. 03 · Article-level text

    Acts come split into articles (content.articles) next to the full text, so your product can cite a provision, not a whole act.

  4. 04 · Search by meaning

    Semantic search over legislation and case law. Legislation hits are single articles. Case-law searches filter by court, date and ECLI. You do not run your own embeddings or vector index.

  5. 05 · Honest about the text

    A document held without text says why in textAvailability instead of arriving empty. The source’s attribution, including which text is legally authentic, travels with every document.

  6. 06 · Kept in sync

    LexAPI syncs the Netherlands with wetten.overheid.nl and Rechtspraak open data on a daily schedule. You do not maintain a crawler or a parser for each source format.

  7. 07 · REST or MCP, from any stack

    Call the national routes over REST from any language or agent framework, or through the LexAPI MCP server in Claude, Cursor, VS Code and other MCP clients.

§ III — What You Can Build

Built for products that cite the law.

Grounded answers (RAG)
Retrieve the Dutch articles that answer a question with POST /api/v1/nl/legislation/semantic, then give your model the text, the id and the attribution so it can cite them.
Case-law research
Find Dutch decisions on a fact pattern with POST /api/v1/nl/search/semantic, filtered by court and date.
Monitoring, EU and national
List the newest Dutch documents with GET /api/v1/nl/documents (newest first) and follow EU changes with LexAPI webhooks, in one product.
Citation checks
Resolve a cited act with GET /api/v1/nl/documents/{id} and check inForce and validTo before your product quotes it.
§ IV — Sources & Licences

Where it comes from.

SourceLicence / termsPublisher
Basiswettenbestand (BWB)Public domain (CC0)KOOP — wetten.overheid.nl
Rechtspraak open dataPublic domain (CC0)de Rechtspraak — data.rechtspraak.nl
Known gaps
  • Case law is the selection de Rechtspraak chooses to publish, not every ruling.
  • Consolidated texts are not the authentic Staatsblad / Staatscourant publication.
  • Decentralised regulations (provinces, municipalities, water boards — CVDR) are not included.
§ V — One Request

The Netherlands, as JSON.

Request
curl -H "x-api-key: $LEX_KEY" \
  "https://lex-api.com/api/v1/nl/documents/NL-BWBR0001854"

NL-BWBR0001854 is a regeling, by its BWB id. A document costs 1 credit (reserved at 5 and settled at 1 when the answer is sent, so a document read needs 5 credits available); list the Netherlands’ documents with GET /api/v1/nl/documents.

Response · abridged
{
  "document": {
    "id": "NL-BWBR0001854",
    "jurisdiction": "NL",
    "language": "nl",
    "documentKind": "act",
    "title": "…",
    "documentType": "…",
    "ecli": …,
    "eli": …,
    "dateOfDocument": …,
    "version": 1,
    "fetchedAt": "…",
    "validTo": …,
    "inForce": …,
    "decision": null,
    "content": { "fullText", "articles", … },
    "textAvailability": { "available": true },
    "attribution": "…",
    "textBasis": …
  }
}
§ VI — Access

On every plan, Free included.

PlanNational-law calls
Free30 calls / month
Starter500 calls / month
Professional2,000 calls / month
Business · Scale · EnterpriseNo separate limit
  • On Free, Starter and Professional, every call to a national documents or semantic route counts as one call, per account and UTC calendar month; the allowance resets at the start of each month (UTC). Business, Scale and Enterprise have no national counter.
  • On every plan, calls use credits from your pool at the normal weights: 3 per listing page, 5 per semantic search, and 1 per document (reserved at 5 and settled at 1 when the answer is sent, so a document read needs 5 credits available).
  • National documents in the citation graph (a national id on /api/v1/citations/…, or ?includeNational=true) are on Business, Scale and Enterprise only.
§ VII — Questions

Frequently asked.

N° 01Is there an API for Dutch law?

Yes. KOOP publishes the consolidated regulations on wetten.overheid.nl with an SRU search service, and de Rechtspraak runs an open-data API for its published decisions. LexAPI reads that data and serves the Netherlands’ consolidated acts and regulations in force (Basiswettenbestand) and published court decisions from de Rechtspraak as structured JSON through one REST API, in the same document shape as every other country it covers and next to EU law from EUR-Lex. Start with GET /api/v1/nl/documents.

N° 02Is wetten.overheid.nl and Rechtspraak data free to use?

Yes. The Basiswettenbestand and Rechtspraak open data are both public domain (CC0). Consolidated texts are not the authentic Staatsblad / Staatscourant publication. LexAPI charges for the API (structure, search, sync), not for the data, and includes the source’s attribution in every document and search response.

N° 03How do I search Dutch case law by meaning?

Send a question or fact pattern in plain language to POST /api/v1/nl/search/semantic. It returns the closest decisions with court, date, ECLI and a snippet; filter with court, date_from, date_to or ecli. Legislation works the same way at POST /api/v1/nl/legislation/semantic, with article-level hits. Each search costs 5 credits.

N° 04Can AI assistants such as Claude use Dutch law through LexAPI?

Yes. Claude, Cursor and other MCP clients reach Dutch law through the LexAPI MCP server (@lexapi/mcp); the MCP page shows the setup. Any model with tool (function) calling can use it too: give it a tool that calls GET /api/v1/nl/documents/{id} or POST /api/v1/nl/legislation/semantic with your API key, and it can quote Dutch law with its source. The official Python and TypeScript SDKs cover the national routes from version 0.4.0.

N° 05How much does the Dutch law API cost?

Dutch law is on every plan. The Free plan includes 30 national-law calls a month, Starter 500 and Professional 2,000; Business, Scale and Enterprise have no separate national limit. Calls also use credits from your monthly pool: 1 credit per document (5 credits must be available when you ask), 3 credits per listing page, 5 credits per semantic search. See pricing.

N° 06How current is the Dutch data?

LexAPI syncs the Netherlands with wetten.overheid.nl and Rechtspraak open data on a daily schedule, picking up new and changed documents. The time of the last sync is on this page and in the public coverage feed (GET /api/v1/national/coverage, no API key needed).

N° 07Which Dutch courts are covered?

Published court decisions from de Rechtspraak. The courts included, and the first year, are listed on this page and in the coverage feed. It is the selection de Rechtspraak publishes, not every ruling.

⁂ ⁂ ⁂

One API key,
EU and national law.

Start on the Free plan: 30 national-law calls a month are included, next to EU law.

LexAPI MCP server → EU and national law in Claude, Cursor, VS Code and other MCP clients