Skip to content

Octrooicentrum Nederland (NL/RVO) — national
Layer national
Jurisdiction NL (WIPO ST.3: NL)
Issuing body Octrooicentrum Nederland (Netherlands Patent Office), a department of the Rijksdienst voor Ondernemend Nederland (RVO), itself an agency of the Dutch Ministry of Economic Affairs and Climate Policy
Rights administered patent, supplementary protection certificate (SPC, incl. paediatric extension), semiconductor topography. NOT trademark / design — those are Benelux-administered by BOIP (see §2).
Working languages Dutch (primary), English (eRegister dual-language; German and French listed in the help index but not implemented on the about page)
Connector status skipped (no programmatic surface; NL patents already covered transitively via EPO OPS / EP Register via the daily NL→FRS feed)
Last verified 2026-05-18
Manifest entry not listed in coverage/sources.yaml — NL is covered transitively via WO/EPO

Detail surveys:

Higher layers covering this office transitively:

  • EPO OPS / INPADOC / EP Register (via regional/epo.md) — NL patent biblio + family + legal events for EP-NL validations, and the NL Patent Office feeds a daily delta of selected NL bibliographic data to the EPO's Federated Register Service (eRegister About page). This is the canonical indirection: NL data reaches programmatic consumers through the EPO, not RVO.
  • EUIPO TMview / DesignView (via planned regional/euipo.md) — Benelux trademarks and designs administered by BOIP flow into TMview/DesignView via the EUIPN Common Tools Integration back-office bridge. BOIP-administered records reach agents through the EUIPN tools, not a BOIP API.
  • EUIPO — EUTMs designating NL+BE+LU and Community designs (RCDs / REUDs). Benelux-only TMs and designs remain BOIP-exclusive on the registration side.
  • WIPO Madrid Monitor / Hague Express — Madrid IRs designating the Benelux territory; Hague IRs designating BX.
  • UPC (via shipped upc_decisions connector) — Netherlands is a UPC contracting state (UP system started 2023-06-01); UPC-routed disputes affecting NL are reachable via that connector.

Rating: 🔴 Red — No API

BPP eRegister is Struts2 server-rendered; structured outputs limited to saved-search RSS + per-document XML download requiring opaque docId from prior HTML search + 1,000-row CSV export. NL feeds a daily delta to EPO Federated Register — coverage closes transitively via EPO OPS. Jump to access details → View on the atlas →

§1 Mission

Octrooicentrum Nederland (OCNL) is the Dutch national patent office — the only authoritative registrar for NL national patents (since 1912), NL Supplementary Protection Certificates (including paediatric extensions), and NL semiconductor topographies. It runs the Netherlands Patent Register on the Benelux Patent Platform (BPP), an IT system shared with the Belgian and Luxembourg patent offices. Trademark and design protection in the Benelux territory is not run by RVO — it is administered by the separate Benelux Office for Intellectual Property (BOIP) at boip.int, a Benelux Organization for Intellectual Property body. Because the Netherlands is an EPC contracting state, an EU member, and a UPC contracting state (UP system live since 2023-06-01), most "Dutch patents" in commercial circulation are EP-routed (covered by EPO OPS), most "Dutch trademarks" of any scale are EUTMs (covered by EUIPO), and the NL Patent Office itself explicitly feeds a daily bibliographic delta to the EPO's Federated Register Service. OCNL's genuine value-add for agents is the NL-national-only slice — NL national patents that never went EP, NL SPCs at register fidelity, NL semiconductor topographies, and live NL file history — none of which has a public API.

§2 What's unique here

  • NL national patents (Octrooi) — published Dutch applications and patents since 1912; not routed through EP. Per WIPO INSPIRE NL Dutch PCT national-phase entry is only available via an EP.
  • NL SPCs + paediatric SPCs — register-fidelity legal status (e.g. "lapsed" on a specific date because of non-payment), not in INPADOC.
  • Registered topographic designs for semi-conductor products — niche but real.
  • Live NL file history / dossier — accessible through the eRegister "Documents" tab; not in EPO OPS.
  • NL patent gazette — De Industriële Eigendom — weekly PDF via the Octrooi-informatie Portal; the Bijblad bij De Industriële Eigendom is the quarterly supplement.
  • Benelux trademarks and designs administered by BOIP — Benelux-territory rights (BE+NL+LU) that are not EUTMs and not Madrid IRs; the registration is genuinely Benelux-administered, even though the data surfaces through TMview/DesignView via CTI.

§3 Programmatic surfaces

Every NL/RVO and BOIP surface is 🔴 Red against the zero-infra-proxy constraint. There is no documented public REST/JSON/XML API for NL patents, NL SPCs, Benelux trademarks, or Benelux designs, and zero entries from RVO or BOIP in the WIPO IP API Catalog (probed 2026-05-18 via /api/apis?size=200: 179 office APIs across DPMA, EPO, EUIPO, IP Australia, JPO, MOIP Korea, QAZ, UPRP, USPTO, WIPO — zero from NL or BX).

Surface Right(s) Endpoint Auth Format Rating
BPP eRegister (NL register search) patent / SPC / topography mijnoctrooi.rvo.nl/fo-eregister-view (Struts2 .action POSTs) none server-rendered HTML; per-doc XML download; CSV export capped at 1,000 rows; per-saved-query RSS subscription 🔴
Octrooi-informatie Portal — gazette patent rvo.nl/octrooiportal none PDF only (weekly De Industriële Eigendom, quarterly Bijblad) 🔴
data.overheid.nl — octrooiregister-nederland-01 patent data.overheid.nl (CC-BY 4.0) none contentUrl is the same Struts2 UI; fileFormat: XLS is nominal; description "Output in xsl of rss"; dateModified: 2020-03-27 🔴 (dormant metadata pointing at the UI; not a bulk feed)
BPP Portal (RVO front door) patent mijnoctrooi.rvo.nl/bpp-portal/en none Drupal 11 navigation site; links to eRegister, MyPage, eOLF, news 🔴 (no data surface)
MyPage (applicant dossier portal) patent mijnoctrooi.mypage.rvo.nl personal applicant-side only 🔴 (not a search surface)
Online Filing eOLF patent efiling.mijnoctrooi.rvo.nl personal filing forms 🔴 (not a search surface)
BOIP register / search (Benelux TM + design) trademark / design boip.int/en/search none, but Google reCAPTCHA gates robots.txt and the site root HTML 🔴 (captcha-gated; no developer page; no /api)

Material details for the most consequential surfaces:

  • BPP eRegister About page (primary source, text verbatim 2026-05-18): "The NL Patent register provides a daily feed of selected bibliographical data on European patents in Netherlands to the Federated Register Service of the European Patent Office." This is the architectural fact that drives the strategy — NL's structured data already reaches programmatic consumers through EPO indirection.
  • eRegister structured outputs (UI-side only). Client JavaScript at /fo-eregister-view/resources/scripts/exportToCSV.js hard-codes maxExportResults = 1000 for the CSV export endpoint (/fo-eregister-view/download/exportCSV) and exposes a per-document XML download at /fo-eregister-view/download/downloadFileXML that requires an opaque docId from a prior HTML search. The "RSS" button is a saved-search subscription, not a general feed.
  • All /api, /rest, /swagger-ui.html, /v3/api-docs probes return 404 on both /fo-eregister-view/ and /bpp-portal/ (probed 2026-05-18). No developer page anywhere on the RVO subdomains.
  • data.overheid.nl entry is metadata-only. The JSON-LD distribution contentUrl points back at the Struts2 search UI; dateModified: 2020-03-27; there is no bulk download behind the dataset link. License is CC-BY 4.0.
  • BOIP gates its site behind reCAPTCHA. boip.int/robots.txt and boip.int/sitemap.xml both return a captcha challenge HTML page. There is no developer portal at /en/developers, no /en/open-data, and no BOIP entry on the WIPO catalog. BOIP's TM and design records reach the public through EUIPN TMview / DesignView via the EUIPN Common Tools Integration back-office bridge — i.e. through EUIPO infrastructure, not a BOIP-operated API.

§4 Fees

Policy: link only. Reproducing fee amounts is not our job.

RVO/Octrooicentrum publishes a fee schedule (in EUR) for NL patents (filing, search, examination, grant, renewals), NL SPCs (filing, renewal, paediatric extension), and miscellaneous services (file inspection, certified copies, priority documents). BOIP publishes its own fee schedule (also in EUR) for Benelux trademark and design filings and renewals.

§5 Access via patent-client-agents

What we cover today

  • NL patent biblio + family + legal events — transitively via patent_client_agents.epo_ops (country code NL). Particularly strong because RVO explicitly feeds a daily delta of NL bibliographic data to the EPO's Federated Register Service.
  • EUTMs designating NL and Community designs (RCD/REUD) — transitively via the planned EUIPO connector.
  • Madrid IRs / Hague IRs designating BX — via planned WIPO Madrid / Hague connectors.
  • UPC-routed disputes touching NL — via shipped upc_decisions connector. NL is a UPC contracting state, UP system live 2023-06-01.

What we should add

Nothing in the form of a direct RVO or BOIP connector. The rating is 🔴 Red — red_no_api for both surfaces — there is no programmatic surface to proxy, BYOK, or contract against. Connector status: skipped.

If we want richer NL coverage beyond what EPO OPS / EUIPO / WIPO already provide, the realistic avenues are to monitor RVO/BOIP for a developer-programme announcement and to stand up a separate NL substantive-law layer via wetten.overheid.nl (out of scope for this synopsis — Rijksoctrooiwet 1995 is the patent statute; the BCIP governs Benelux TM/design).

Next steps

  1. Watch WIPO IP API Catalog for any RVO or BOIP entries — the canonical signal an IP office has shipped a public API.
  2. Watch the BPP portal news feed at mijnoctrooi.rvo.nl/bpp-portal/en/news-page for a developer-programme announcement (none as of 2026-05-18).
  3. When the EUIPO connector lands, confirm Benelux TM / design records surface via TMview / DesignView at the expected fidelity; document any BOIP-specific fields that don't make it through CTI.
  4. Re-evaluate when any of those signals fires. Until then, route NL patent queries through EPO OPS and document the NL-national-only patent / SPC / topography / file-history gap as a known limitation.

§6 Known unknowns

  • Bilateral "Data Delivery" path. Did RVO ever publish a private licensable interface (analogous to IPI's signed-ToU API in Switzerland or the JPO BYOK pattern)? Institutional pages are silent; worth a direct enquiry to octrooien@rvo.nl before final closure.
  • NL→FRS feed completeness. The eRegister About page says RVO sends "selected bibliographical data on European patents in Netherlands" daily to FRS. Does that include NL national-only patents (not EP), NL SPCs, NL topographies — or just EP-NL? Probe needed: pull a known NL-national patent (e.g. NL 1015875, the worked example on the WIPO INSPIRE PDF) through EPO OPS and confirm coverage.
  • BOIP CTI fidelity in TMview / DesignView. When EUIPO connector lands, audit what BOIP fields make the CTI round-trip vs. drop in transit. Class headings, Benelux-only renewal events, and legal-status nuance are the typical losses on CTI bridges.
  • BPP cross-leg coverage. BPP runs three legs (NL, BE, LU); all three look identical in behaviour. Worth confirming whether the BE leg (bpp.economie.fgov.be/fo-eregister-view/) and the LU leg (patent.public.lu/bpp-portal/) ever ship divergent endpoints — a "common API" announcement covering BX would be the leading indicator.
  • NL legal-status fidelity vs. INPADOC. Per WIPO INSPIRE, legal status like "lapsed for non-payment of annual fee" is canonical from the NL register. Does INPADOC ingest the event code + reason, or only the lapse-date? Empirical probe needed.

§7 References

Primary sources only — rvo.nl, mijnoctrooi.rvo.nl, octrooicentrum.nl, data.overheid.nl, wetten.overheid.nl, boip.int, apicatalog.wipo.int, inspire.wipo.int, euipn.org.

Service overviews:

Substantive rights:

Open data + portal entries:

Cross-office context:

Detail surveys + waves:

Last updated 2026-05-18.