Vol. II·Section N — National Law Desk

§ National Law — Country Coverage

National law,
same API.

Legislation and case law from national legal orders, read from public open-data sources and served next to EUR-Lex: the same API key, the same credit pool, one document shape. Countries go live one at a time; the list below shows which are live.

In short

LexAPI is a REST API for EU law that also serves national legislation and case law, read from each country’s official open-data sources and returned as structured JSON in one document shape for every country. One API key and one credit pool cover EUR-Lex, CJEU case law and every live country. The live list is below and at GET /api/v1/national/coverage.

§ I — Coverage

Country by country, as it goes live.

Each country page lists its sources, licences and known gaps. A country in preparation is not available through the API yet.

§ II — Access by Plan

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.

The national-source terms apply to every account. Details in the API documentation.

§ III — Endpoints

Four routes, plus a public coverage feed.

{jur} is the lower-case country code (at, de, nl, …). Which countries are live, and what each covers, is at GET /api/v1/national/coverage: public, no API key, no credits, not counted against the allowance. Authentication, errors and credits work as for the EU endpoints: see the API documentation.

EndpointWhat it returnsCredits
GET /api/v1/{jur}/documentsList a country’s documents, newest first (summaries). Query: q (title contains), type (documentType contains), limit (1–100, default 20), cursor (the previous page’s nextCursor, any depth) or page (the first 1,000 results only), includeRepealed=true to include repealed acts.Credits 3
GET /api/v1/{jur}/documents/{id}One document, the same shape for every country: documentKind (act | decision), title, documentType, ecli, eli, dateOfDocument, inForce / validTo; decision (court, case numbers, cited norms); content (fullText, articles); textAvailability; attribution. Optional ?language=.Credits 1 *
POST /api/v1/{jur}/search/semanticCase law by meaning. Body: query (3–1000 chars), limit, min_score, filters { court, date_from, date_to, ecli }, include: ["text"].Credits 5
POST /api/v1/{jur}/legislation/semanticLegislation by meaning, article-level hits (up to 50). Body: query, limit, min_score, filters { id, inForce, documentType }.Credits 5

* reserved at 5 and settled at 1 when the answer is sent, so a document read needs 5 credits available.

Request
curl -H "x-api-key: $LEX_KEY" \
  "https://lex-api.com/api/v1/at/documents/AT-NOR-10001597"

Ids carry the country prefix (AT-NOR-10001597 is a federal act, by its RIS Gesetzesnummer). Every document and semantic-search response carries the source’s attribution, which says when a consolidated text is not the authentic one. Listing responses are summaries without it.

Response · abridged
{
  "document": {
    "id": "AT-NOR-10001597",
    "jurisdiction": "AT",
    "language": "de",
    "documentKind": "act",
    "title": "…",
    "documentType": "…",
    "ecli": …,
    "eli": …,
    "dateOfDocument": …,
    "version": 1,
    "fetchedAt": "…",
    "validTo": …,
    "inForce": …,
    "decision": null,
    "content": { "fullText", "articles", … },
    "textAvailability": { "available": true },
    "attribution": "…",
    "textBasis": …
  }
}
§ IV — How It Works

Built for software that cites the law.

01 · Public open-data sources

Each country comes from public open-data sources, under the reuse terms or statutory copyright exemptions its country page lists. The source travels with every document as attribution.

02 · One document shape

Every country answers with the same fields, types and formats: id, act or decision (documentKind), title, ECLI and ELI, date, court and case numbers for decisions, the same article fields for acts, and inForce / validTo. A field a country’s source lacks is null, never missing.

03 · Honest about gaps

A document we hold without text says why in textAvailability instead of serving an empty shell. What a source does not cover is listed on its country page.

Why not read each source directly?
  1. 01 · EU and national law on one key

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

  2. 02 · 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.

  3. 03 · Search by meaning

    Semantic search over national legislation (article-level hits) and case law, where a country’s coverage lists it. No embeddings or vector index to run.

  4. 04 · 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.

LexAPI is a data API for developers and AI builders: it gives your product the text of the law and where it came from, so answers can cite it. It is not legal advice and does not make anyone compliant.

⁂ ⁂ ⁂

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