User-visible changes to LexAPI — the REST API, the dashboard, and the MCP server. Grouped by month, newest first. For request/response details see the API docs and the OpenAPI spec.
Entries that change the API contract name the contract version they introduced (API x.y.z, the OpenAPI info.version and the X-LexAPI-Version response header). How the numbers work: Versioning & changelog. Deprecations get their own entry headed Deprecated:, with the replacement and the removal date (at least 180 days after it is published) — see Deprecations.
November 2026
/documents/recent limit; /info on daily-call plans (API 3.1.0)
#- Changed:
GET /api/v1/documents/recentwith alimitthat does not start with a number (limit=abc,limit=) or is negative is a refunded400 INVALID_PARAMS; it answered a charged200. Every otherlimitis read as before. - Changed: on daily-call plans (accounts from before credit pricing),
GET /api/v1/infono longer counts against the daily limit and is answered when the limit is used up;usage.unitsChargedis0. Credit plans are unchanged. - Docs: a document published only moments ago can answer
404 NOT_FOUND: try again in 10 minutes.
Every change since 2.18.1, in one release (API 3.0.0)
#Released 22 November 2026. The API moves from 2.18.1 to 3.0.0, still under /api/v1. Nothing is removed or renamed; credit costs are unchanged. API 2.18.2 to 2.30.0 were not released on their own; they ship together as 3.0.0. What an existing integration or account may notice:
API behaviour
#- Document reads (2.21.0) — an unreadable document gave
404or a text-less200→ refunded502/504/500(batch items:UPSTREAM_ERROR,TIMEOUT,INTERNAL);404means it does not exist. Do: retry with backoff, honourRetry-After; keep treating404as final. PAYMENT_PAST_DUE(2.27.0, 2.29.2) — after a failed payment, keys were refused at once (403 { "error": "Subscription inactive" }) → they work for up to 7 days, then get403 PAYMENT_PAST_DUEuntil the payment succeeds or the subscription ends; accounts already past due at the release stay refused. Do: branch oncode; showbillingUrl.inForceon/legislation/semantic(2.19.0) — ignored →truekeeps only acts known to be in force today; a non-boolean is a400. Do: send a boolean or omit it./documents/:celex/at/:date(2.28.0) — some dates return another snapshot; new refunded404boundary_unknown; impossible dates and non-EUlanguagecodes are a400. Do: treatboundary_unknownlikebefore_tracking.asOfon/:jurisdiction/legislation/semantic(2.29.0) — ignored → applied; an invalid value is a400, not charged. Do: sendYYYY-MM-DDor omit it./search,/parse,/documents/recent(2.21.0, 2.28.1, 2.30.0) — a failed search could look like a result → refunded502;erroris an object or a string. Do: retry; accept both shapes./citations/extract(2.21.0) —success: truewith an incomplete count → refunded502. Do: retry./resolve(2.21.0) — a failed ECLI lookup was a404→ refunded500. Do: retry.asOfon/legislation/semantic(2.19.0, 2.22.0, 2.23.1, 2.25.0) — more hits unresolved (in_force_dates_unknown,not_yet_in_force, newamendment_not_consolidated); somenot_in_languagehits resolve. Do: accept unknown reasons; use the text only ifasOfResolvedistrue.fetchedAton document reads (2.20.0) — response time → when the text was fetched. Do: do not use it as the request time.fetchedAtof past versions (2.28.0) — last fetch → when the version was first observed, where known (alsoobservedFrom). Do: do not read it as "last checked".include: ["text"]on/search/semantic(2.30.0) — a hit without text had nosnippet→ keeps it, withtextAvailability. Do: readtextAvailability.- OAuth scopes (2.28.1) — not required → a token without the route's scope gets
403 TIER_FORBIDDEN; existing connections holdlex; API keys have none. Do: nothing. - JSON without its content type (2.24.0) — the
400/422adds a hint, maybe amessagefield. Do: sendContent-Type: application/json; do not match error bodies exactly.
Billing and credits
#- Past due (2.28.1) — set at every failed payment → only when the subscription is past due or unpaid; monthly credits do not renew meanwhile. Do: pay the open invoice.
- Top-up credits (2.26.1, 2.29.2) — untouched by resets → spent after the monthly credits: each credit reset (monthly, at a plan change, or by LexAPI) deducts those used; the rest stay while the paid plan is active. A refunded purchase removes its credits. Balances at the release are kept. Do: nothing.
- Automatic top-ups: charging (2.26.1) — not charged → buys a pack when the balance runs low, at most three times per monthly credit cycle, once you confirm the terms and the dashboard shows charging as active. Do: confirm, or switch it off.
- Automatic top-ups: switched off (2.29.2) — now when a charge is declined, needs your bank's confirmation or cannot be made with the card on file, when a paid subscription ends, or when the account moves to FREE or a plan arranged with LexAPI. Do: switch it on again if wanted.
- Top-up checkout (2.28.1) — now needs an active subscription, else
409 SUBSCRIPTION_NOT_ACTIVE. Do: pay the open invoice first.
SDKs and MCP server. The releases that match API 3.0.0 are @lexapi/client 0.5.0, lexapi-client 0.5.0 and @lexapi/mcp 0.6.0. Earlier releases (0.4.0, 0.4.0, 0.5.1) keep working without an upgrade; with them a past-due account gets an error with code PAYMENT_PAST_DUE (the SDKs raise LexAPIError). See each package's changelog before upgrading: TypeScript, Python, MCP.
New
#POST /api/v1/legislation/as-of(2.26.0); in-force label and filter (2.19.0);provenance(2.20.0);observedFrom(2.28.0); nationalasOflabels (2.29.0);/inforesult caps (2.24.0); dashboard invoices.
Fixed
#- Semantic search for FREE accounts marked past due (2.29.3); two
500s, and a credit reset is applied only once (2.30.0); an entry into force dated before the act (2.22.0).
Versioning policy. From 3.0.0, a behaviour change an existing integration may notice ships in a MAJOR version under /api/v1, without a notice period, and is listed in that version's entry. Nothing is removed or renamed without a deprecation of at least 180 days: Versioning & changelog.
Some document reads may be slower for about a day after the release; they are not charged more.
Case-law text availability, /documents/recent types, two 500s fixed, versioning policy (API 2.30.0)
#include: ["text"]onPOST /api/v1/search/semantic: every hit carriestextAvailability; a hit without text keeps itssnippet(from the machine-written summary, not court text). Same cost./documents/recentnames an unknowndocumentTypeinignoredDocumentTypesandX-Ignored-DocumentTypes, as/searchdoes; it still filters nothing and is charged as usual.- Fixed: two
500s —/searchwith somedocumentTypevalues (now answered) and/documents/recentwith an invaliddays(now a refunded400); a credit reset is applied only once. Versioning policy: see API 3.0.0.
Semantic search on a FREE account marked past due (API 2.29.3)
#- Fixed: some FREE accounts got
403 TIER_FORBIDDENon semantic search.
Billing: payments that failed before this release; top-up refunds and automatic top-ups (API 2.29.2)
#- The up-to-7-day period applies to payments that fail from API 3.0.0 on; an account already past due stays refused until the payment succeeds or the subscription ends.
- A refunded top-up purchase removes its credits (a partial refund, its share; the balance never goes below zero).
- Automatic top-ups switch off when a paid subscription ends.
Docs: asOf wording (API 2.29.1)
#- Docs: with
asOf,POST /api/v1/legislation/semanticreturns for each hit the version listed for the date, asPOST /api/v1/legislation/as-ofdoes; the docs said "the version in force".
National semantic legislation search: asOf labels (API 2.29.0)
#asOfonPOST /api/v1/:jurisdiction/legislation/semantic(1800-01-01to today): a hit isasOfResolved: trueonly when the publisher's dates show today's wording applied on that date.- The search covers today's texts only: for a provision amended since, LexAPI cannot return the earlier wording. An unresolved hit keeps its text. That text is today's wording; it is not established as the text for the date.
- LexAPI holds such dates for Austria and Spain; for the other countries every hit is
asof_not_available. Same cost. Reasons andcheckedAt: API docs.
Error responses: the credits figures (API 2.28.1)
#creditson an error response may show the charge before an automatic refund; a later response shows the refunded balance. Details: Errors.
GET /documents/:celex/at/:date: correct snapshot for the date; clearer answer (API 2.28.0)
#- Fixed:
/at/:datereturns the snapshot LexAPI held at the end of that day (UTC); some dates now return a different one. - Added:
observedFromon every version; on/at/:datealsodocument.observedUntil(when the document's next version arrived),dateInFutureand, for EU acts,inForceLookup(a pointer to/legislation/as-of);reason: "before_tracking"on the404for a date before tracking. - Changed: a date LexAPI cannot place is a refunded
404boundary_unknown; a date that does not exist (2026-02-31) or a non-EUlanguageis a refunded400. This is LexAPI's fetch history, not the law in force. 1 credit. A404costs 1 credit, exceptboundary_unknown, which is refunded. API docs.
Errors: PAYMENT_PAST_DUE documented; unknown endpoints marked (API 2.27.0)
#PAYMENT_PAST_DUE(403) is now a documented error code, withbillingUrland, when known,accessEndedAt: the answer after the up-to-7-day period that follows a failed payment, until it succeeds.- Unknown endpoints: the
404for a path or method the API does not have carrieserror.details.reason: "unknown_endpoint"; its status and code are unchanged. - Docs correction: truncated exports. Page a truncated
/exportwith consecutivedateFrom/dateTowindows, notchangedSince; run one that endstruncatedBy: "recovered"again.
Billing: failed payments, invoices in the dashboard
#- Up to 7 days to fix a failed payment. When a subscription payment fails, your API keys keep working for up to 7 days. The dashboard shows the exact time.
- Invoices in the dashboard, each with its PDF; Manage billing for every account with billing history.
Top-up credits and automatic top-ups (API 2.26.1)
#- Top-up credits are spent after the monthly credits; each monthly reset deducts those used, and the rest stay while your paid plan is active.
- Automatic top-ups (paid self-serve plans): the dashboard shows the terms (at most three charges per monthly credit cycle), asks you to confirm them, and shows when charging is active.
POST /legislation/as-of: the version of an EU act for a date, and one provision of it (API 2.26.0)
#- New endpoint:
POST /api/v1/legislation/as-of. Send an EU act's CELEX number and a date;asOfVersionnames the version listed for that date (the newest consolidated version, or the act as published). Addprovision(art_17) for one article, annex or recital. Unresolved:asOfResolved: falsewith anasOfReason, no text. - It does not say whether a provision applied on that date. Consolidated versions are documentation without legal force; only the act as published in the Official Journal is authentic.
- Costs 1 credit without a text fetch; with one, 4 (5 live), or 1 if it fails or finds no text; up to 5 are reserved meanwhile. API docs.
asOf: a hit stays unresolved when an amendment is not consolidated (API 2.25.0)
#- New
asOfReason:amendment_not_consolidatedonPOST /api/v1/legislation/semanticwithasOf: an amending act may have applied on that date, and no consolidated version listed for the date is known to include it. The hit keeps its indexed text, which is not established as the text for the date. - Regulations, directives and decisions. Same cost; clients that ignore unknown
asOfReasonvalues need no change.
/info lists every endpoint and the semantic result cap; clearer error for JSON sent without its content type (API 2.24.0)
#/info:subscription.maxSemanticResults(case law) andsubscription.maxSemanticLegislationResults(legislation, at most 50) are the most results one semantic search returns on your plan;endpointsalso lists/citations/transposition/:celexNumberand/citations/counterparts/:id(listed while a country is open to your account).X-LexAPI-Client: an optional header for integrations to name themselves; it never affects authentication, credits or limits. JSON sent withoutContent-Type: application/jsongets a hint in its400or422.- Docs: the official SDKs (0.4.0 or later) cover the national routes.
asOf: consolidated versions that only add corrigenda in other languages (API 2.23.1)
#- Fixed: with
asOf, some hits answerednot_in_languagealthough the act has a text in force in that language; they now resolve (for example English hits of32018R1725). Same cost.
Provenance: fetch time on national documents, EU licence (API 2.23.0)
#In-force label: corrigenda, entry into force, end dates (API 2.22.0)
#- Corrigenda carry the in-force label of the act they correct, and
inForce: truekeeps them when that act is in force. - Fixed: an entry into force recorded before the act's own date is ignored (the Digital Services Act now reads
not_yet_in_forcefor anasOffrom 19 October to 15 November 2022).endOfValidityis left out when several end dates are recorded.
A 404 only when the document does not exist (API 2.21.0)
#- A
404now means the document does not exist. When a document cannot be read,/documents/metadata,/documentContent, batch items and/documents/urlanswer502 UPSTREAM_ERROR,504 TIMEOUTor500 INTERNAL, refunded in full. A404still costs 1 credit. - Same rule elsewhere:
/citations/extract,/search,/parseand/documents/recentanswer a refunded502instead of an incomplete result; a failed ECLI lookup on/resolveis a refunded500. - The
502s of document reads and/citations/extractcarryRetry-Afterwhen the wait is known. Details: Errors.
Provenance on every document (API 2.20.0)
#- New object
provenanceon documents and semantic hits:publisher,sourceUrl,sourceIdentifier,retrievedAt,contentHash,versionIdentifier,language,licence— always all eight keys,nullwhere a value is not known. National documents and hits carry it too, with the source and licence thatGET /api/v1/national/coveragelists. - New object
fieldProvenance: which fields are the publisher's text (official_source_text) and which were derived (machine_extracted_structure,machine_generated_interpretation,editorial_enrichment); LexAPI serves no machine translations. Additive; same cost. Details: Provenance.
In-force label on EU legislation (API 2.19.0)
#- New fields
inForce,notInForceReason,endOfValidity,entryIntoForceonPOST /api/v1/legislation/semantichits and on document reads: whether the act is in force today (UTC), as recorded by the Publications Office; left out when not known. They do not cover amendments or dates of application. No extra credits. - New filter
inForce: true: only hits whose act is known to be in force today; the others are counted ininForceFilter, so a page can be shorter thanlimit. Same cost.
Semantic legislation search: what you get without asOf (API 2.18.2)
#- Docs: without
asOf,POST /api/v1/legislation/semanticreturns the indexed texts as they are (the act as published, or its latest consolidated version where indexed), not "the latest version". For the text in force today, pass today's date (UTC) asasOfand use the hits withasOfResolved: true.
Spec clarifications (API 2.18.1)
#- Wording only, no behaviour change: the API docs and the OpenAPI descriptions are shorter; every limit, credit cost, header, parameter and error code is unchanged.
Connect apps with your LexAPI account (OAuth) (API 2.18.0)
#- "Log in with LexAPI" for MCP clients. LexAPI is now an OAuth 2.1 authorization server, so the hosted MCP server (
https://mcp.lex-api.com/v1) can be connected to Claude and other MCP clients by signing in and approving, instead of pasting an API key. Every plan can connect, Free included. How to connect, what you approve and what it costs: Connect with OAuth. - Dashboard → Connected apps lists each connected app with its last use and its requests and credits for the last 30 days, and disconnects it immediately. Connections don't count toward your plan's API-key limit.
- Account security. We email you whenever a new app is connected, and resetting your password disconnects every connected app (API keys keep working). We also email you when a connected app's sign-in looks unusual; if you don't recognise it, disconnect the app. Desktop apps that return through an app link (such as Cursor's
cursor://…) are supported and always ask for approval. - REST API. API keys work exactly as before, and the OAuth tokens are usable only through the hosted MCP server. One visible change: a request to
/api/v1whoseAuthorization: Bearervalue is shaped like a JWT (and carries nox-api-key) and doesn't authenticate now gets401with"error": "Invalid access token"and aWWW-Authenticate: Bearer realm="lexapi", error="invalid_token"header, instead ofAPI key required; an API key sent asBearer lex_…gets the same answer as before. The authorization server's endpoints (/.well-known/oauth-authorization-server,/.well-known/jwks.json,/oauth/*) are new and sit outside/api/v1.
National coverage: citation figures no longer missing after a restart (API 2.17.2)
#GET /api/v1/national/coverage:citationGraphcould briefly readnull; such an answer is nowCache-Control: no-store.
Spec clarifications (API 2.17.1)
#- Wording only, no behaviour change:
GET /api/v1/citations/counterparts/:idfollows the EU acts a national document is linked to by atranspositionorimplementationedge — one its national source records, or a measure notified to the Commission — rather than "the EU acts it transposes or implements"; a notification is not a finding that the measure transposes the act. Theviaandtruncateddescriptions say the same. The exampleX-LexAPI-*headers show the current version.
/resolve: ELIs looked up in Cellar, qualified CELEX kept (API 2.17.0)
#POST /api/v1/resolvelooks an ELI up in Cellar:http://data.europa.eu/eli/dec/2019/166/ojnow answers32019D0003(01), not the non-existent32019D0166. Corrigendum ELIs (…/corrigendum/2018-05-23/oj) resolve to the corrigendum (32016R0679R(02)), consolidated-version ELIs (…/2016-05-04) to that version (02016R0679-20160504), an ELI written with the parent type (eli/reg/2019/947/ojforeli/reg_impl/2019/947/oj) to the same act; language or format segments are optional. An ELI Cellar has no work for returns404.- A bare CELEX that names a distinct work is kept as given:
32019D0003(01)no longer resolves to32019D0003(a different act), and32016R0679R(02)and02016R0679-20160504no longer return404. Every CELEX/resolvereturns resolves to itself. - New response field
verified:truewhen the mapping was confirmed,falsewhen the CELEX was read off the identifier. NewresolvedViavalueeli-cellar;elinow means an unconfirmed ELI mapping. An ELI that cannot be checked and has no pattern to fall back on returns502 UPSTREAM_ERROR(refunded). Still 1 credit.
National semantic search: incomplete searches are labelled (API 2.16.0)
#POST /api/v1/:jurisdiction/search/semanticand/:jurisdiction/legislation/semanticlabel a search the national index could not finish. With nothing to return, the answer is503 NATIONAL_SEMANTIC_UNAVAILABLEwithpartialReason: "SEARCH_INCOMPLETE"(withRetry-Afterwhen a retry may help) or the new422 NATIONAL_SEMANTIC_FILTER_UNREACHABLE(rephrase the query or change the filters), refunded in full with the national call given back. With some hits left, it is a200withpartial: true,partialReason: "SEARCH_INCOMPLETE"and ahint, charged as usual. A complete answer never carriespartial.
Spec clarifications (API 2.15.1)
#- Wording only, no behaviour change: for an
agent-auditedmethod the re-check is a separate blind review by a person working with a second AI agent; the country pages say "re-checked in a separate blind review" instead of "re-checked by hand".
Citation graph: who labelled the checked links (API 2.15.0)
#GET /api/v1/national/coverage:citationGraph.precisiongainsreview—human(people labelled the links) oragent-audited(an AI model labelled them and a separate blind review re-checked a sample);nullwithout labels — and, foragent-auditedonly,audit: the re-check'ssize,done,falseAccepts,disagreementsandagentReviewed(links that rest on the model's verdict alone). A method whose re-check finds a wrongly accepted link is reported ashuman, on its human labels alone.
Citation graph: small methods checked in full (API 2.14.0)
#GET /api/v1/national/coverage:citationGraph.precisiongainscensus:truewhen every link of the method was checked, soerrorUpperBoundis the exact error rate;falsefor a sample;nullwithout labels.
Spec clarifications (API 2.13.1)
#- Wording only, no behaviour change:
countsSourceiscountedwhenever acitationType,provenanceorresolutionfilter is set, not onlycitationType(and, with national documents in scope, while withdrawn national documents are filtered out;jurisdictionsalone keepsstats); the older error shape now lists the fields the citation routes already send —paramandallowedon a400 INVALID_PARAMSfor an unknown filter value, andpartial,partialReasonandtimeoutMson the/citations/counterparts503 TIMEOUT; the exampleX-LexAPI-*headers show the current version.
Citation graph: rates that cannot be measured (API 2.13.0)
#GET /api/v1/national/coverage:citationGraph.methodsgainsunmeasured: the rates a country's sources do not let LexAPI measure, each with a reason code (not-collected,source-empty); those rates arenull, with no floor. The Netherlands declaresdecisionsToActsand SloveniaactsToEuasnot-collected.actEuRateisnull, with no floor, for a country whose only EU method istext-pattern: its acts carry no recorded EU references to measure, andtextPatternRatemeasures its EU references (the Netherlands).
Citation graph: published floors and the notified-measure match rate (API 2.12.0)
#GET /api/v1/national/coverage:citationGraphgainsfloors: the lowest value each rate (decisionsToActs,actsToEu,textPattern,nimResolved) is expected to stay at;nulluntil set.textPatternRateon the same block: the share of the EU act numbers found in running text (with their EU marker) that produced an edge, from the last full rebuild (measuredAt);nullbefore one ran — the rate thetextPatternfloor applies to.nimResolvedRateandnimMeasuredAton the same block: the share of the measures the member state notified to the Commission, among those in scope for LexAPI's matching, that were matched to a document LexAPI holds — from the last matching run that went through all of the country's measures;nullwithout one.precision.provenance(sourceorresolver):precisionalways describes a method of the country's own citation extraction, never the matching of notified measures.
Citation graph across borders: transposition, counterparts, provenance (API 2.11.0)
#GET /api/v1/citations/transposition/:celexNumber(5 credits, every plan): the measures the member states notified to the Commission for an EU act (CELEX sector 3), grouped by country, from the Publications Office's Cellar records of the notifications — all 27 member states and the United Kingdom, with one measure shape for every country. Every answer carries thenote: "Measures are those the member state notified to the Commission for this act. A notification is not a finding that the measure transposes the act, or transposes it completely." On BUSINESS, SCALE and ENTERPRISE, for live jurisdictions, it also says which measures LexAPI holds (id,resolved,resolution,resolutionBasis,counts.resolved,source.lanes) and adds the documents whose national source records that they transpose or implement the act (provenance: "source");resolvedOnly=truekeeps only the held ones. Below BUSINESS, for a jurisdiction that is not live, and while the national-source terms are not accepted (termsRequired: true, not a 403) those fields arenull. Measures Cellar no longer lists are left out.GET /api/v1/citations/counterparts/:id(20 credits, BUSINESS and above): a national document's counterparts in the other live jurisdictions, through the EU acts it transposes or implements — ranked 1 (the national source records the relation), 2 (a notified measure LexAPI holds), 3 (a notified Cellar record LexAPI does not hold). An EU act as:idlists its own measures the same way. A lookup that runs out of time is a503 TIMEOUT(partial: true,partialReason: "TIMEOUT"), refunded.- Provenance and resolution on every edge.
citations[]on/cited-byand/cites, and the newedgeDetails[]on/networkneighbours, carryprovenance(notice,cellar,notice+cellar,cellar-nim,source,resolver) andresolution(id,key,abbreviation,text-pattern;nullon EU edges). Every node carriesid,jurisdictionanddocumentKind;celexNumberis unchanged. - New filters on
/cited-by,/cites,/network,/pathand/related:jurisdictions(eu,at,de— a national code impliesincludeNational=true, same plan gate),provenanceandresolution(comma-separated), andcitationTypenow takes a comma-separated list too. The new typetranspositionis in thecitationTypeenum. An unknown value is a400 INVALID_PARAMSnaming the parameter and its allowed values (refunded). unresolved=trueon/citesand/networkfor a national document id addsunresolved— the references the document records that LexAPI could not turn into an edge (for example a code LexAPI does not hold), at most 500, withunresolvedTruncated. A national id that is not visible to you (a jurisdiction not live for you, a withdrawn document) never appears in it. No extra credits./citations/statswithincludeNational=trueaddsbyJurisdiction,byProvenanceandtransposition(measures,resolved,byCountry— counted with the/citations/transpositionrule).GET /api/v1/national/coveragegainscitationGraphper live country: the extractionmethods,edges,decisionResolutionRate,actEuRate,transposition(measures,resolved),precision(the labelled-sample error bound of the resolution method) andmeasuredAt— measured values only,nullwhere nothing was measured.
Spec clarifications (API 2.10.1)
#- Wording only, no behaviour change: the
domainparameter's description says what EUR-Lex's ownNATIONAL_LAWcollection is (member-state measures transposing EU directives and member-state case law, as EUR-Lex indexes it); the national document-id examples name real ids of the launch countries; the national allowance headers say UTC calendar month.
Citation graph: where the totals come from (API 2.10.0)
#countsSourceonGET /citations/cited-by,/citesand (inpaging)/network:statswhentotalCitations/totalEdges(and the network'scitesTotal/citedByTotal/citesEdgeTotal/citedByEdgeTotal) were read from maintained per-document counts, orcountedwhen they were counted for the request (always with acitationTypefilter). Both are exact for the request; the totals keep their meaning and stay integers.nullon a partial/networkresponse, like the totals.- The undocumented edge type
citesno longer exists; those edges arereference, the documented value. No documented response changes.
National law: texts withheld by the source (API 2.9.1)
#- A national document whose source withholds its text now answers
content: nullwithtextAvailability: { available: false, reason: "no_machine_readable_rendition" }, instead of serving the source's notice as the text. First case: Lithuanian register acts whose only "text" was "Teisės akto tekstas neskelbiamas …". A text the register publishes later is served. No new field or reason value; the spec's national No text description says so (a clarification, API 2.9.1).
National law: where a document's text was read from (API 2.9.0)
#content.textSourceandcontent.ocronGET /api/v1/{jurisdiction}/documents/{id}, two more keys of the onecontentshape — always present.textSourcesays where the text was read from, for countries whose source publishes some documents only as PDF:html(the source's web rendition),pdf-text(the text layer of the source's PDF) orocr(machine-read from a scanned page);nullfor countries that do not label their text — none of the countries live today sets it yet.content.ocrisnullunlesstextSourceisocr; then it names the engine, its version and recognition model, the recognitionconfidence, the pages read and anotice: OCR text may contain recognition errors and is never the official text. A scan recognised below the country's confidence floor is not served as text (content: null,textAvailability.reasonno_machine_readable_rendition).
National law: one document shape for every country (API 2.8.0)
#- Every national response has the same fields, types and formats in every jurisdiction, so one integration works for all of them. Every documented field is always present: a field the source does not provide is
null(or[]), no longer left out —ecli,eli,dateOfDocument,validTo,inForceandtextBasisincluded. documentKind(act|decision) on the listing, the document and every semantic hit'sdocument: one vocabulary for legislation and case law.documentTypestays the source's own label.decisiononGET /api/v1/{jurisdiction}/documents/{id}: a decision'scourt,chamber,caseNumbersandcitedNorms({ text, documentId }), read from whichever fields the source uses (Austria'sgericht, Germany'saktenzeichen, Slovenia's case number inside its ordinal…);nullfor acts. Served also when a decision has no text.contenthas one shape.fullText,articles,textLanguages,textLanguage,embeddedForeignText,repeal,sourceanddetails— always all of them. Every article is{ number, title, section, text, inForceFrom, inForceTo, details }; a unit whose text the source does not publish hastext: null. What a source adds beyond these fields (its own names for chambers, summaries, unit ids, cited-norm lists) moved undercontent.detailsandarticles[].details, unchanged.- National semantic search: every hit carries
document, the matched document as the listing returns it. Legislation hits always carrylaw_title,article_ref,section,language,in_force,valid_from,valid_toandlaw_type,nullwhen the index has nothing for the unit.
National law: the language of a document's text (API 2.7.0)
#content.textLanguages,content.textLanguage,content.embeddedForeignTextonGET /api/v1/{jurisdiction}/documents/{id}, now described in the spec. Dutch treaties (NL-BWBV…) list the languages BWB publishes their text in (["en"]for a treaty published only in its authentic English text,["en", "nl"]with a Dutch translation).textLanguageis set when the whole text is in one language other than the document'slanguage;embeddedForeignTextistruewhen the text includes text in another language.- A court decision whose source publishes no text (rechtspraak.nl: metadata only, or a judgment declared void; RIS: a decision page whose text sections are all empty) is a
200withcontent: nullandtextAvailability.available: false, no longer an empty text.
National law: withdrawn documents, a cursor listing (API 2.6.0)
#- Withdrawn documents are a
410. A document its source withdrew (for example a court decision taken down to fix its pseudonymisation) is served nowhere.GET /api/v1/{jurisdiction}/documents/{id}answers410 DOCUMENT_WITHDRAWNwith only the id, the jurisdiction andwithdrawnAt— no title, no text — and the read is refunded in full. The listing and national semantic search leave it out. On the/citationsroutes a withdrawn national id is a410before anything is charged, and edges to it are left out ofincludeNational=trueresults. Delete any copy you hold. - The listing pages by cursor.
GET /api/v1/{jurisdiction}/documentsis ordered newest first by the document's own date (undated last) and pages withcursor/nextCursor(andhasMore) to any depth.pageserves the first 1,000 results only.totalis counted up to 10,000, withtotalExactsaying whether it is exact.qtakes 3–200 characters. A malformed query is a400before anything is charged or counted; a page that takes too long is a refunded504 TIMEOUT. The cost is unchanged: 3 credits per page. - New error code
DOCUMENT_WITHDRAWN(410), in both error-code enums of the spec. /citations: a national id of a country that is not live answers its404withcode: "NOT_FOUND"too (theerrorstring is unchanged).- National legislation semantic search validates
hydelike the case-law route: anything but a boolean is a400, andhyde: trueis answered with"hyde": falseat 5 credits.
Launch: national law, country by country — 3 November 2026 (API 2.5.0)
#This is the national-law launch entry. LexAPI now serves national legislation and case law alongside EU law, under the same API key. Countries open one at a time: which are live, and what each covers, is at lex-api.com/national-law and GET /api/v1/national/coverage.
- New endpoints.
GET /api/v1/{jurisdiction}/documents(list, withq,type,includeRepealed,page,limit),GET /api/v1/{jurisdiction}/documents/{id}(one document with its text,textAvailabilityandattribution),POST /api/v1/{jurisdiction}/search/semantic(case law) andPOST /api/v1/{jurisdiction}/legislation/semantic(legislation).{jurisdiction}is the lower-case country code. A country that is not live answers with the same404as an unknown path. - Coverage endpoint.
GET /api/v1/national/coverage— public, no API key, no credits — lists each jurisdiction withlive,launchedAt, legislation and case law separately (scope, document counts, start of coverage, courts), whether semantic search is available, the sources with their licence and required attribution, andlastSyncAt. - Every credit plan. FREE, STARTER and PROFESSIONAL get national law within a monthly allowance of national calls — FREE 30, STARTER 500, PROFESSIONAL 2,000 per UTC month — reported in
X-National-Limit,X-National-RemainingandX-National-Reset. A used-up allowance is a402with the new codeNATIONAL_ALLOWANCE_EXHAUSTED, before any credit is charged. A failed call gives its national call back by the credit-refund rule (every 5xx, every 4xx except 404). BUSINESS, SCALE and ENTERPRISE have no separate limit. - Costs. A listing page 3 credits; a document read charged 5 and settled at 1 (always our own corpus); national semantic search 5, flat — national indexes have no HyDE, so
hyde: truecosts 5 and answershyde: false. - Citation graph.
includeNational=trueon/citations/cited-by,/cites,/network,/path,/relatedand/statsadds national documents of live jurisdictions, where the national source records the links. BUSINESS, SCALE and ENTERPRISE only (403 TIER_FORBIDDENbelow); the allowance does not cover the graph. - New error codes.
NATIONAL_ALLOWANCE_EXHAUSTED(402),NATIONAL_SEMANTIC_NOT_ENABLED(409: semantic search is not available for that country; refunded) andNATIONAL_SEMANTIC_UNAVAILABLE(503: the country's index is temporarily unavailable; refunded). Both error-code enums in the spec include them. /infolists the national endpoints, with the jurisdictions open to you, once at least one country is live.- Licences and permitted use. Each national source has its own licence; every national response carries the
attributionto keep when you republish. Consolidated national texts are not the authentic ones. You must not re-identify anyone a court has anonymised or pseudonymised, and analytics on French judges and court clerks (art. 33 of loi n° 2019-222) are prohibited — see Terms §7 and National law in the docs.
October 2026
Free plan: 500 credits to start, then 150 a month
#- From 30 October 2026, new accounts start with 500 credits for their first 30-day cycle. After that, the Free plan includes 150 credits every 30 days. Unused credits do not carry over, as before.
- Existing free accounts keep 500 credits until the end of their next credit period after 30 October, then move to 150. The dashboard shows when the current period ends.
- An account that moves to Free from a paid or trial plan gets 150 a month, with no starting grant. Paid plans, top-ups and the 15 requests a minute on Free are unchanged.
MCP server 0.3.0: 26 tools and a hosted endpoint
#@lexapi/mcp0.3.0 is on npm and in the MCP Registry asio.github.Lex-API/lexapi-mcp. It grows from 10 tools to 26: document batches, observed versions,resolve, bulk export (BUSINESS and above), citation paths, related documents and graph stats, citation extraction, webhook management, and your plan and credit balance. Each tool is billed like the REST endpoint it wraps.- Hosted server. No local install needed:
POST https://mcp.lex-api.com/v1(Streamable HTTP), with your API key asAuthorization: Bearerorx-api-key. It serves all 26 tools. - Read-only mode.
LEXAPI_MCP_READ_ONLY=truehides citation extraction and the four webhook writes, leaving 21 tools.
Setup and the full tool list: MCP server.
Contract fixes from the SDK and MCP audit (API 2.4.0)
#Billing and timeouts
#- Document reads get a 90-second deadline.
/documentContent,/documentContent/batch,/documents/urland/documents/metadataanswer504 TIMEOUTafter 90 seconds, refunded in full (the last two answered a500before). - Failed batch items are refunded, each like a single
/documentContentcall that failed the same way:NOT_FOUNDcosts 1 credit, a timeout or upstream error is refunded. A national-law id is reported asUNSUPPORTED_JURISDICTIONand not charged. - Batch
errors[]entries carry a typedcode(NOT_FOUND,UNSUPPORTED_JURISDICTION,TIMEOUT,UPSTREAM_ERROR,INTERNAL), pluscelexNumberandmessage.celexanderrorstay as they were. - The batch headers add up. A new
X-Batch-Failedheader counts theerrors[]entries, andX-Batch-Live-Fetchesno longer counts failed items. Corpus-Hits + Cellar-Served + OJ-Recovered + Live-Fetches + Failed now equalsprocessed. - A timed-out citation network is refunded in full.
- Documented: what is not refunded. A
5xxLexAPI did not send, and a dropped connection, are not refunded. Every5xxLexAPI sends is refunded in full.
Errors
#- Every 429 carries a stable
code.RATE_LIMITEDis the per-minute limit, withRetry-After/retryAfteras before. The newQUOTA_EXHAUSTEDis a legacy daily-call plan's used-up daily quota or monthly semantic quota. It addsresetsAt(omitted when the reset time is not known to be in the future) and, as before, carries noRetry-After— the official SDKs and the MCP server recognise a quota by that absence and don't retry it. A monthly semantic quota whose billing period on record has already ended has noresetsAtat all: key off the top-levelcode, as the current SDKs do. Older SDK releases that look only forusage.resetsAttreat that one case as a rate limit and retry it. - Legacy-shape errors carry
code. The routes whoseerroris still a string (429s, the semantic endpoints,/searchvalidation and failures,/documents/recentfailures, the batch's body validation, the citation routes' failures) now also sendsuccess: falseand the stable code as a top-levelcode. Nothing was removed. The docs list exactly which routes use which shape. - Semantic queries of 1–2 (or over 1000) characters are a
400, not a502, and so is afilters.date_from/date_toon/search/semanticthat cannot be read. /citations/path:maxDepthof 0, a negative or a non-integer is a400. It used to be read as 3, and negatives went straight through. Values above 8 are still clamped to 8; an empty value still means 3, and3.0counts as 3.
Responses
#usage.unitis sent:creditson credit-pool plans,callson legacy plans. The docs described it, but it was never there.include: ["metadata"]keepsdocumentTypeCode, andparagraphsis documented as a validincludetoken (it always worked)./documents/metadatacleans placeholder authors on corpus reads too. "Provisional data" is dropped, as on/documentContent.GET /webhooks/:idrecentDeliverieshas the documented delivery shape.- Citation paging is deterministic, and counts what it pages. Edges are ordered newest first with a unique tiebreaker, so offset pages no longer repeat or skip rows. A new
totalEdgeson/cited-byand/cites(andpaging.citesEdgeTotal/citedByEdgeTotalon/network) counts the rows thatoffsetpages over.totalCitationscounts distinct document pairs, which can be fewer. /infolists every endpoint family: semantic search, versions and export were missing. Theauthorlist now includescivil-service-tribunal./documents/recentsays when it narrows a filter. A repeateddocumentTypeorsubdomainhas only ever applied one value, the first valid one. It now says so in anX-Warningheader (see the deprecation below).
Spec and docs corrections (no behaviour change)
#- The citation endpoints' CELEX path parameter accepts corrigenda (
32013R0952R(04)) and consolidated texts (02016R0679-20180524), as the routes always have. SubscriptionTierincludesSCALE.Authorincludescivil-service-tribunal.DocumentByUrlRequestdocumentsbypassCorpus.DELETE /webhooks/{id}is documented as the200 { success, message }it returns, not204.402 CREDITS_EXHAUSTEDis listed on every metered route, not only/legislation/semantic.- Semantic
filterslists the keys the semantic service applies. Case law:date_from,date_to,court,case_number,ecli,language. Legislation reads onlylanguage. The case-law example usedyear_from, which was never applied. - The semantic tier caps include FREE (10).
partieson semantic case-law hits is documented as the array of strings it is. Also documented:summary_language, the legislation hits'id,snippet,chapter,sectionandexact_match_law_id(alwaysfalseon this endpoint), andmatchedVersion.id. - Also documented:
hasResume/hasSummaryandtitleSourceon citation groups and nodes, thelanguageparameter on citation reads, andlanguageFilter.partialMetadataKept. The headersX-Language-Filter,X-Language-Kept,X-Language-Partial-Kept,X-Cache-Age,X-PostFiltered-Kept(author:3/10;date:2/3) and everyX-Sourcevalue (corpus,cellar,cellar-oj,live) are documented too. /search: a list ofsubdomains is matched as any of, except on answers without anX-Search-Sourceheader, which apply only the first./documents/recentlimits, now stated:author=general-court/civil-service-tribunalis not filtered there (you get all case law of the window), andimplementing,proposalandguidelinematch only their first EUR-Lex form./searchhandles both.cited-bycompleteness: its edges are refreshed on read, andrelationSync: pendingmeans a recent amendment may not be listed yet.- The docs now describe the time limits per fetch and per request.
Deprecated: GET /api/v1/documents/recent with more than one documentType or subdomain (API 2.4.0)
#- Send one value per request, or use
POST /api/v1/search, which accepts lists./documents/recenthas only ever applied the first of several values. The others were dropped without notice. The spec has always declared both parameters single-valued, while these docs said "string / list". - Nothing changes yet. A repeated parameter still gets its first valid value, now with an
X-Warningnaming the ignored ones. Its responses carry the deprecation headers (X-LexAPI-Deprecations: recent-multi-document-type/recent-multi-subdomain). A single value is unaffected. - No removal date is set. When one is, it will be at least 180 days after it is published here. After it, the multi-value form gets
410 GONE. We email the accounts that sent a repeated parameter.
Changed: bulk export is charged per row, as documented (API 2.3.0)
#GET /api/v1/exportnow costs 1 credit per row written, at least 1 per export. The docs have always said "1 credit per row", but the server charged 1 credit per export call, whatever the number of rows. Credit plans now pay what the docs say. On legacy daily plans an export still counts as one call against the daily quota. An export now writes the usage row that makes it count, including an export you abort.- How the charge works. The request is admitted for 1 credit, which pays for counting the matching rows; an empty pool is a
402 CREDITS_EXHAUSTEDbefore anything is counted. Then it reserves the rest of 1 credit for every row it can return: the matching rows, capped atlimitand the 50,000 server maximum. The newX-Export-Credits-Reservedheader and_meta.creditsshow the reservation. When the stream ends, every reserved credit beyond max(rows written, 1) is refunded: rows skipped as metadata-only stubs, rows that disappeared during the export, rows not sent because you disconnected. If the export fails on our side, you pay for the rows written only. The settled charge is on the trailer, in the new_done.credits(reserved,charged,refunded, plus the pool after settlement).refundPending: truemarks a refund that is applied automatically within minutes. - Low balance. If your pool cannot cover the reservation, the request fails with
402 CREDITS_EXHAUSTEDbefore anything streams, the same as a search whose pages your pool cannot cover. The admission credit is kept, because the count ran.error.details.weightis the reservation anderror.details.availableyour balance; pass alimitat or below it. - Counts never cap the export. Rows added after the count are streamed too, each reserved as it comes; an export the pool cannot keep paying for streams as many rows as it can still pay for, then ends with
truncated: true, truncatedBy: "credits". A count that takes longer than 15 seconds returns504 TIMEOUT; the 1-credit admission is kept. - A failed export has no trailer. If an export fails after streaming has started, the stream now ends cleanly without a
_doneline; before, the connection was left open. An export is complete only if it ends with_done. The official SDKs raise an incomplete-export error when it is missing. _done.truncatedreports truncation correctly. It counted skipped stubs as rows cut off by the cap, so an export that had reached every matching row could saytruncated: true. It now means matching rows were not reached because oflimitor the server maximum; the newtruncatedBysays which (limit,max_rowsorcredits). Stub rows beyond the last row written do not count either.skippedStubsis unchanged.truncatedBy: "recovered". If an export is stopped on our side while it is still streaming (for example after a stalled connection), the stream stops at the next page and ends withtruncated: true, truncatedBy: "recovered". The recovery's refund of the reservation stands, so_done.credits.chargedcan be belowwritten; re-run the export from the last row you received.- New parameter
changedSince. Only rows whose text changed (a new version) at or after this time. It is the cheapest incremental sync under per-row billing.fetchedSincekeeps its documented meaning (lastSeenAt: any write to the row, including metadata refreshes and re-checks that left the text unchanged). - New parameter
documentTypeCodeselects a type family.regulationcoversRegulation,Implementing regulation,Delegated regulationand the Commission implementing/delegated labels; likewisedirectiveanddecision. documentTypeCodevalues for implementing and delegated acts. Documents labelledImplementing regulation,Delegated regulation,Implementing directive,Delegated directive,Implementing decisionorDelegated decisionnow carrydocumentTypeCoderegulation,directiveordecisionin every response, like the Commission implementing/delegated labels already did. They used to carryimplementing_regulation,delegated_regulationand so on.- Fixed:
documentTypeandauthorwere case-sensitive. The docs' own example,documentType=regulation, matched nothing because the stored label isRegulation. Both now match whole stored values, ignoring case.documentType=regulationreturnsRegulationdocuments only; usedocumentTypeCodefor the family. A joint act's author is one value:author=European Parliament, Council of the European Unionselects it as a whole. - Fixed:
dateFrom/dateTonow select by document date. Rows without a document date are left out of a dated export. - Malformed parameters are now a
400 INVALID_PARAMS, not charged: adateFrom/dateTothat is notYYYY-MM-DD, afetchedSince/changedSincethat is not ISO 8601 with a timezone, alimitthat is not a positive integer, and a repeatedlanguage.
Changed: webhook URLs must be public HTTPS endpoints (API 2.2.0)
#- Webhook
urls must be publichttps://endpoints on port 443 or 8443, without credentials in the URL, on a public hostname or IP address.POST /webhooks,PUT /webhooks/:idandPOST /webhooks/:id/testanswer400 WEBHOOK_URL_NOT_ALLOWEDwithdetails.reasonwhen a URL doesn't qualify, and aFAILEDorPAUSEDwebhook can only be set back toACTIVEonce its URL does. - A delivery to a URL that no longer qualifies fails (
errorMessagestartingWebhook URL not allowed) and is retried like any failed attempt. Webhook reads carry a newurlErrorfield naming the problem with a stored URL. - Redirects are not followed. A
3xxanswer is a failed delivery; point the webhook at the final URL. responseBodyin test results and delivery history now holds the first 500 characters of your endpoint's reply only when its content type is text, JSON or XML (text/*,application/json,+json,application/xml,+xml;nullotherwise), stored as received rather than re-serialized. Test results gaindurationMs.
API versioning and deprecation policy (API 2.1.0)
#- Every response now names the API version.
X-LexAPI-Versioncarries the contract version the server implements (2.1.0), andX-LexAPI-Releasethe deployed build — that version plus the commit it was built from, e.g.2.1.0+633eb67. Both are sent on errors and on/healthas well. Quote the release when you report a problem. - The contract version follows semantic versioning from here on. A MINOR bump adds something (endpoint, optional parameter, response field, enum value, header), a PATCH bump corrects the spec without changing behaviour, a MAJOR bump marks a breaking change. Every bump gets an entry here. 2.1.0 is the first version under this policy; earlier changes are listed under the months below.
GET /api/v1/inforeturns the contract version asversion(2.1.0), the same value as the header./healthnow reports the release asversion, plusapiVersion,commitandbuiltAt.- A deprecation policy. Additive changes ship at any time; breaking changes only under a new major path (
/api/v2). Anything under/api/v1that is retired is deprecated first and keeps working for at least 180 days after its removal date is published. The 180 days are enforced in code: a removal date is refused unless it is at least 180 days after the day it is published, and CI refuses a publication date in the past. Responses that use a deprecated endpoint, parameter or field carryDeprecation(RFC 9745),Sunset(RFC 8594, once a date is set),Link: <…>; rel="deprecation"(andrel="successor-version") andX-LexAPI-Deprecations. After the removal date the request gets410 Gonewith the new error codeGONE, naming the replacement. We email the accounts that used it in the previous 90 days when it is deprecated, and again when a removal date is set. Details: Deprecations. - Browser clients can read these headers. CORS now exposes
X-LexAPI-Version,X-LexAPI-Release,Deprecation,Sunset,LinkandX-LexAPI-Deprecations. - changelog.md is built from this file on every deploy.
Deprecated: POST /api/v1/parse (API 2.1.0)
#- Use
POST /api/v1/searchinstead./parseis the original name of the search endpoint, kept as an alias: same handler, same request body, same response, same price. It is now listed in the OpenAPI spec asdeprecated: true, and its responses carry the deprecation headers above (X-LexAPI-Deprecations: parse-endpoint). - No removal date is set. It keeps working. When a date is set, it will be at least 180 days after it is published here. We email the accounts that called
/parsein the previous 90 days now, at deprecation, and again when the date is set.
Semantic legislation search: consolidated texts and the text in force on a date
#- One hit per article when the act and its consolidated version both match. The legislation index now holds the latest consolidated versions alongside the acts as published in the Official Journal. When both match the same article,
/legislation/semanticreturns one hit: the consolidated article, labelledconsolidated,consolidatedAsOf,baseCelexandconsolidatedNote. The act as published is underbaseAct, at the higher of the two scores. Consolidated texts are not authentic; the Official Journal text is. - New
asOfparameter (YYYY-MM-DD). Each hit answers with the version in force on that date. That is the act as published before its first consolidation, or the consolidated version in force. Hits that cannot be answered for that date keep their latest text, withasOfResolved: falseand anasOfReason. The response addsasOfandasOfSummary. - What
asOfcosts. The search costs 5 credits, as before. A version our corpus does not hold is fetched live, by default at most 3 per request. Each live fetch is billed like a document read for the same outcome: 4 or 5 credits, 1 when there is no text, 0 when it fails. A fetch your pool cannot cover is skipped, and that hit isinsufficient_credits.
Title language label (titleLanguage)
#- New
titleLanguagefield on document, batch and metadata responses. Some documents have no title in the language you asked for, for example a corrigendum that corrects only the Dutch version. We then show the title from a language that has one, and this field now names that language (enfor the English fallback of a non-English request, or e.g.nl). It is absent when the title is in the requested language, andinclude: ["metadata"]keeps it.
Fixed: article titles, section headings and author on consolidated texts
#- Article titles on consolidated texts. Some consolidated versions (e.g.
02025R0202-20260101) returned every article withtitle: nulland the title at the start ofcontent;titleis now set. - Section headings no longer stick to the previous article; they go to
paragraphs[]. authoris no longer"Provisional data"or"Not available". Both are placeholders for consolidated texts, not institutions./documentContent,/documents/metadata,/documents/recent,/searchand webhook payloads now returnauthor: nullfor these documents. If a real author is listed alongside it, only the real author is kept. The base act (CELEX3…) still carries its real authors. This applies to documents already in our corpus as well.- The article title and section heading fixes apply to consolidated texts fetched from now on.
Citation graph: complete amendment links from Cellar
#- Amendment, corrigendum and repeal edges for legislation now come from the Publications Office's Cellar repository, and a new
relationSyncfield on/citations/cited-byand/citations/networksays how current they are (fresh,refreshed,pending, …). Same price. - New
citationType: "corrigendum". Corrigenda (32008R1272R(01),…R(02), …) used to be counted as amendments. They now have their own type, and each corrigendum is a separate citing document. Their titles are in the language(s) each corrigendum was published in. - English titles on these edges wherever Cellar has one; other languages are used only when no English title exists.
- Fixed: wrong document dates on
/documents/recent. Since late September, many rows carried another document'sdateOfDocument, and the list order was off with them; some/searchanswers were affected the same way. Dates and ordering are correct again. If you stored dates from these endpoints since 22 September, re-fetch them.
Pointer from a text-unavailable base act to its consolidated version
#- New
textAvailability.latestConsolidated(andupcomingConsolidated). When a legislation base act (CELEX sector 3 — e.g. REACH32006R1907, CLP32008R1272, or a qualified id such as32019D0003(01)) answersavailable: falseon/documentContent,/documentContent/batchor/documents/url, the block may now name the act's newest consolidated version (CONSLEG, e.g.02008R1272-20260701) — the act with its amendments integrated — plus the next one when the Publications Office has published it ahead of its date. Pass thecelexback to/documentContent; that is a normal, separately charged read. - The hint is free and best-effort. No extra credits; omitted when the lookup doesn't answer, so its absence proves nothing.
source: "corpus"marks an answer from our own rows while the Publications Office was unreachable (may not be the newest version). - It does not guarantee text. A consolidated version is its own document and can itself be
too_largeornot_in_language. Consolidated texts are documentation without legal value of their own — the authentic text is the one in the Official Journal. /documents/metadatacarries the same fields only when a recent document read already looked them up.
September 2026
Search & recent documents
#- Unfiltered
/documents/recentrequests settle at a single page: 3 credits whatever thelimit, at most 200 rows per call, markedX-Source: cellar. Requests filtering ondocumentType,author,domainorsubdomainare still priced per page (X-Source: live). /searchnames the source that answered inX-Search-Source(API docs); acellaranswer bills one page. A search answered from our corpus comes back withpartial: true,source: "corpus"andX-Search-Source: corpus: the list may be incomplete, and text is matched against titles only. If nothing can answer, the request fails with a full refund (504 TIMEOUTor500), never an empty list presented as "no results".- Identical searches are cached for an hour. The same filters and
maxPageswithin 60 minutes are served from a result cache (X-Search-Cache: hit|miss|bypass;fetchedAtstays the real fetch time; same price). Passfresh: trueto force a re-fetch.query: "*"is now treated as "no text constraint". - Fixed: since 2 August,
/searchanswers from the EUR-Lex web service (X-Search-Source: soap) returned too few results foryear/monthand none fordomain: "EU_LAW".year/monthnow filter on the document date, andEU_LAWadds no restriction. Re-run searches made since 2 August. - Fixed: day-level date ranges. Some searches returned a whole month for a one-day range; those results are now trimmed to your
dateFrom–dateTo.
Plans & billing
#- Annual plans reset their monthly credits every month, as the pricing page says.
- Plans we grant by hand (managed plans) no longer show self-serve billing screens (billing portal, top-ups, automatic top-ups). Plan changes made by our team send you an email naming the new plan, monthly credits and next refresh date.
August 2026
Credit pricing: Cellar-served answers now settle at 4 credits
#- Three-tier settlement on document reads. Every document fetch, by-URL fetch, metadata call and batch item is charged 5 upfront and settles by who answered it: 1 when served from the LexAPI corpus (unchanged — still the typical case), 4 when the EU Publications Office's Cellar API answered (
X-Source: cellar/cellar-oj), and 5 only for a browser fetch of EUR-Lex itself. Previously Cellar answers settled at 1. Batch responses expose the split viaX-Batch-Corpus-Hits/X-Batch-Cellar-Served/X-Batch-OJ-Recovered/X-Batch-Live-Fetches(these four counts now partition the batch exactly). - OJ recovery after a failed live attempt bills the full 5. When a live fetch comes back textless and the text is then recovered from an Official Journal issue, the answer keeps
X-Source: live. - Fixed: batch double-refund on text-unavailable items. Refunds are now exactly one per item.
Documents whose text EUR-Lex doesn't publish
#- Correction to a June entry: until 19 August some documents without text returned
200with a EUR-Lex error page ascontent.fullText(/documentContent, the batch,/documents/urland/exportrows) instead of thetextAvailabilityanswer. - New
textAvailabilityblock on every document response. Usually{ "available": true }. When EUR-Lex publishes a document's notice but not its text, you now get200with full metadata,content: null, anX-Text-Available: falseheader, and a machine-readablereason—not_in_language(with the languages that do have text),not_published_yet,no_machine_readable_rendition, orunknown. Deliberately not a404: the document exists, and/resolve,/citationsand/versionsall answer for it.contentis now nullable — checktextAvailability.availablebefore reading it. - These answers cost 1 credit, not 5. Same price as
/documents/metadata, which is all you received. On batch requests they stay indocuments[]with atextUnavailablecount and anX-Batch-Text-Unavailableheader, rather than being moved toerrors[]where their metadata would be lost. - Parliamentary questions now return their real text. Written and priority questions have no per-document rendition on EUR-Lex — their text is published inside an Official Journal issue. We now extract it (
X-Source: cellar-oj). Questions from before 2012 have no text anywhere upstream and say so. - A request for a language EUR-Lex can't serve now falls back to English properly. Previously the fallback only fired when the whole document was missing, so
language=fron a document with no French text returned the error page instead of the English text. bypassCorpusdoes what the docs said: a forced re-read is now genuinely fresh./exportskips metadata-only rows by default;includeStubs=truerestores the old behaviour, and the export trailer reportsskippedStubs.- Published CELEX pattern corrected. The OpenAPI spec advertised
^[0-9A-Z]{2,20}$, which rejects corrigenda (32013R0952R(04)) and consolidated texts (02016R0679-20180524) that the API has always accepted — generated clients were refusing requests the server would have answered. acceptLanguages: the authentic text in one call. Most General Court decisions have no English text — the authentic text is the language of the case, usually alongside French. PassacceptLanguages(an ordered list of ISO codes, or"any") on/documentContentor the batch endpoint and, when the requested language has no text, the first accepted language that does is served instead — clearly labeled withlanguageRequested,languageFallbackandX-Language-Fallback, the same semantics the automatic English fallback has always used. Off by default: without it you keep thetextAvailabilityanswer with itsavailableLanguageslist./corpuspublishes a third number. Documents held as metadata only — because EUR-Lex publishes no text for them — are now counted separately instead of being folded into "with full parsed text."
July 2026
- Faster, indexable docs & blog.
/docsand every blog post are now served as pre-rendered HTML — instant first paint, working link previews, and reliable search indexing.
June 2026
Pricing v2 — the monthly credit pool
#- New pricing model launched. Plans now come with a monthly credit pool instead of a daily call cap: FREE 500 · STARTER 30,000 · PROFESSIONAL 150,000 · BUSINESS 500,000 credits/month. Operations draw credits by weight — 1 for fetch/search/citations lookups, 2 for citation extraction, 5 for semantic search, 20 for citation network/graph calls.
- Existing customers grandfathered. Accounts created before the cutover keep their daily-call plan; their responses report
subscription.pricingMode: "daily"and nocreditsobject. - Top-up packs. Buy +10k/+50k/+200k credits mid-cycle; top-ups are spent after the monthly allowance and don't expire at the monthly reset; they end with the paid plan. FREE-tier accounts cannot buy top-ups. (How used top-up credits are deducted at each reset changed in API 3.0.0.)
- Semantic search on FREE. On the new pricing, the credit pool gates semantic search, so FREE keys can use it too (legacy FREE keys still get 403).
- Typed 402. When the pool is empty, metered calls return
402 CREDITS_EXHAUSTEDwithoperation,weight,available,used, andresetsAtinerror.details. - Mode-aware stats + docs. Usage/stats endpoints and the docs now speak credits for v2 accounts and daily calls for legacy accounts.
MCP server
#@lexapi/mcppublished to npm. Plug LexAPI into Claude and other MCP-capable agents:npx -y @lexapi/mcpwith your API key.- New resolver & graph tools.
lex_resolve(any identifier → canonical document),lex_citation_path(shortest citation path between two documents), andlex_related(neighborhood exploration).
Account security
#- Email verification is now required. New accounts must verify their email before API keys can be issued.
- Two-factor authentication. Opt-in TOTP 2FA (authenticator app) for dashboard login.
- Self-serve password reset from the Settings page.
API behavior fixes
#- Typed error envelope. Failures on document, search, resolve, and citation routes return
{ success: false, error: { code, message } }with a stable machine-readablecode— a missing document is now always a404 NOT_FOUND, never a placeholder document. See the error catalog. (Partly overstated — see the August 2026 correction: documents whose notice existed but whose text did not still returned a placeholder until 19 August 2026.) languagehonored end-to-end./documentContentlocalizes bothcontent.articlesandcontent.fullText, with explicit English fallback (languageRequested,languageFallback,X-Language-Fallbackheader). Unsupported codes are a typed 400.- Truncation is explicit. Search responses carry
truncated/truncatedAt/truncatedReasonwhen tier caps cut a result set;/exportsetsX-Export-Truncated. Requested document types the engine can't map are surfaced viaignoredDocumentTypes+X-Ignored-DocumentTypesinstead of being silently dropped. documentTypeCode. Documents carry a stable lowercase type enum alongside the displaydocumentType.- Quota visibility.
usage.resetsAtis exposed on successful responses (not just 429s), and every metered envelope reportsunitsCharged. - Semantic
hintfield. Low-confidence or empty semantic results carry a best-efforthintso callers can adjust queries. - Case-law citation graph. Case→case citation edges added — judgments now appear in
cites/cited-by/network results. - Citation network hardening. Long traversals return
200withpartial: true, partialReason: "TIMEOUT"instead of hanging. - Upstream timeouts are typed. Slow EUR-Lex fetches return
504 TIMEOUT(retry-safe) rather than a generic 500. - Search date-range fix. Year-aligned date ranges combined with
documentTypeno longer return 0 results. - Consolidated CELEX accepted. Point-in-time identifiers like
02016R0679-20180524validate correctly. - Case-law text structure.
paragraphs[]for judgment grounds;availableLanguagessurfaced on search hits. /exportparity. Bulk export rows match/documentContentfield-for-field, including thesubdomainfilter.- Field selection.
include/fieldstrims document payloads;articleIdfetches a single article.
Docs & dashboard
#- AI-readable docs. The full reference ships as Markdown at /docs.md plus
llms.txt, with a copy-for-LLM button on/docs. - Credit-aware dashboard. Usage widgets show the credit pool for v2 accounts; usage chart gained a 24h/7d/1m/3m range switch; live
/statuspage.
May 2026
- Document corpus. LexAPI keeps its own copy of the EU corpus with version history;
X-Sourcesays what answered, andbypassCorpus: trueforces a fresh fetch. - Bulk export.
GET /api/v1/exportstreams the corpus as NDJSON with filters and incrementalfetchedSincesync (BUSINESS tier). - OpenAPI 3.1 spec published.
- Password reset emails and the corpus-coverage docs page; site-wide editorial redesign.
Earlier
- February 2026 — Semantic search launched: AI-powered case-law search by meaning, with results enriched with full EUR-Lex text. Promotion codes enabled at checkout.
- November 2025 — Webhooks (signed deltas for saved searches) and citation extraction launched.
- October 2025 — FREE tier introduced; daily limits on paid tiers raised significantly; search API expanded with comprehensive EUR-Lex filters (dates, types, authors, procedures, domains).