EPO Patent Corrections Scraper
Pricing
from $53.60 / 1,000 epo publication deltas
EPO Patent Corrections Scraper
Scrape European patent correction publications (A8/A9/B8/B9) from the EPO: patent, applicant and correction date. Every run returns the current records as a dataset. Optional watch mode returns only what changed since your last run. Pay per result.
Pricing
from $53.60 / 1,000 epo publication deltas
Rating
0.0
(0)
Developer
NexGen Watch
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
16 days ago
Last modified
Categories
Share
β’οΈ EPO Patent Corrections Scraper
Scrape European patent correction publications (A8/A9/B8/B9) from the EPO: patent, applicant and correction date. Run it once and you get the current records as a dataset β that is the default. Turn on watch mode and a scheduled run returns only what changed since the last run (see Optional: run it on a schedule).
Corrected European patent publications (A8/A9/B8/B9). Roughly 50 a week β docketing accuracy rather than bulk.
Output is one epo_publication_record row per result; billing is pay-per-event, the value event being one epo publication delta (a $0.02 start fee per run, then $0.08 per epo publication delta plus one $0.10 source check per run that reads the source). Source: data.epo.org.
Who buys this
Buyers usually search for EPO patent corrections or European patent corrections.
- IP lawyers, paralegals and trademark/patent agents following EPO patent corrections.
- Brand, R&D and competitive-intelligence teams watching European patent corrections.
- IP-data vendors and researchers building dated publication records.
π Sample Output
Real rows from run ViGOHr4AqbzDCNU0m on build 0.1.19 (2026-09-28), the same input as the Quick start below β every value is as the source published it (emails masked, long text shortened):
| publication_id | publication_number | kind_code | kind_meaning | publication_date | delta_slice |
|---|---|---|---|---|---|
| EP4737260W1A8 | 4737260 | A8 | corrected title page of an A publication | 2026-09-23 | correction-publication |
| EP4779709W1A8 | 4779709 | A8 | corrected title page of an A publication | 2026-09-23 | correction-publication |
| EP4790753W1A8 | 4790753 | A8 | corrected title page of an A publication | 2026-09-23 | correction-publication |
| EP4792654W1A8 | 4792654 | A8 | corrected title page of an A publication | 2026-09-23 | correction-publication |
| EP4793243W1A8 | 4793243 | A8 | corrected title page of an A publication | 2026-09-23 | correction-publication |
| EP4793635W1A8 | 4793635 | A8 | corrected title page of an A publication | 2026-09-23 | correction-publication |
| EP4284117W1A9 | 4284117 | A9 | complete reprint of an A publication | 2026-09-23 | correction-publication |
| EP4570819W1A9 | 4570819 | A9 | complete reprint of an A publication | 2026-09-23 | correction-publication |
The run finished with the status message: PARTIAL: emitted 10 item(s); ITEM CAP REACHED: max_items (10) kept 10 of 32 matching publication(s). The rest are not in the baseline. Narrow delta_types or number_prefix, or raise max_items.
β What you get
Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):
record_key(string/null) β e.g.epo:EP4737260W1A8publication_idβ e.g.EP4737260W1A8publication_numberβ e.g.4737260kind_codeβ e.g.A8kind_meaningβ e.g.corrected title page of an A publicationseries_tokenβ e.g.W1publication_dateβ e.g.2026-09-23delta_sliceβ e.g.correction-publicationdocument_urlβ e.g.https://data.epo.org/publication-server/rest/v1.2/patents/EP4737260W1A8/documentrecord_type(string) β e.g.epo_publication_recorddelta_type(string/null) β null in every sample rowdelta_kinds(array/null) β null in every sample row
β What you get
β What you get
record_key(string/null) β e.g.epo:EP4786128W1A8publication_idβ e.g.EP4786128W1A8publication_numberβ e.g.4786128kind_codeβ e.g.A8kind_meaningβ e.g.corrected title page of an A publicationseries_tokenβ e.g.W1publication_dateβ e.g.2026-09-16delta_sliceβ e.g.correction-publicationdocument_urlβ e.g.https://data.epo.org/publication-server/rest/v1.2/patents/EP4786128W1A8/documentrecord_type(string) β e.g.epo_publication_recorddelta_type(string/null) β null in every sample rowdelta_kinds(array/null) β null in every sample row
βοΈ Sample inputs
1. Quick start β the Store example (this is what the sample above came from)
{"weeks": 1,"number_prefix": [],"max_items": 10,"watch_mode": false,"baseline_id": "default"}
The sample run charged exactly: 1 Γ $0.02 apify-actor-start + 1 Γ $0.10 source-check + 0 Γ $0.08 epo-publication-delta = $0.12 on the Free tier β snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.
2. A smaller, narrowed run
{"weeks": 1,"number_prefix": [],"max_items": 5,"watch_mode": false,"baseline_id": "default"}
Caps the run at 5 rows; same billing shape as the sample run above.
3. Optional watch mode (changes only, for a schedule)
{"weeks": 1,"number_prefix": [],"max_items": 10,"watch_mode": true,"baseline_id": "default"}
The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.08 each plus the $0.10 source check; billed deltas are capped at 500 per run.
π§Ύ JSON sample record
One real record from run ViGOHr4AqbzDCNU0m, exactly as it lands in the dataset (emails masked, long text shortened):
{"record_key": "epo:EP4737260W1A8","publication_id": "EP4737260W1A8","publication_number": "4737260","kind_code": "A8","kind_meaning": "corrected title page of an A publication","series_token": "W1","publication_date": "2026-09-23","delta_slice": "correction-publication","document_url": "https://data.epo.org/publication-server/rest/v1.2/patents/EP4737260W1A8/document.html","record_type": "epo_publication_record","schema_version": "1.0","output_mode": "preview","preview_cap": 25,"preview_truncated": 0}
π§ How it works
Source. The actor reads data.epo.org β endpoints: https://data.epo.org/publication-server/rest/v1.2. Public pages and feeds only; nothing behind a login.
Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.
Watch semantics. Snapshot mode (watch_mode: false) returns a preview capped at 25 records. Watch mode keys every record on a source-native id, stores a private baseline in a named key-value store, and on each later run emits one delta row per change (new / changed / removed). A blocked fetch is never diffed, so a source outage cannot show up as a mass removal.
Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape β the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.
Charging. Each epo publication delta is charged at the moment it is pushed (epo-publication-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.
π§ How it works
π§ How it works
Source
EPO publication server, weekly Bulletin publication lists (public, logged-out)
Public, logged-out only β no API key, login, cookie or CAPTCHA.
robots.txt on the publication server permits all paths.
The four delta types, and their weekly volumes
| value | kind codes | measured per week |
|---|---|---|
application-publication | A1, A2, A3, A4 | ~3,700 |
grant-publication | B1 | ~1,900 |
amended-specification | B2, B3 | ~35 |
correction-publication | A8, A9, B8, B9 | ~50 |
The volumes are very uneven and they matter. Selecting
application-publication means roughly 3,700 deltas on the first comparison run,
and billed deltas are capped at 500 per run β so it takes several runs to drain,
each reporting the withholding. If you want a low-volume, high-signal feed, watch
amended-specification (a patent narrowed or upheld after opposition) and
correction-publication.
Kind selection narrows the baselined record set, not just the reporting, so watching B2 stores 35 records rather than 5,767. Because that changes which records exist, the selection is part of the baseline identity: changing it starts a fresh baseline instead of emitting a corpus-wide phantom delta storm.
Fair use
The EPO publishes a 10 GB / 7 days per-IP limit. This actor reads one weekly list
per publication date β about 470 KB each β and the kind code is embedded in the
publication id, so no per-publication document is ever fetched. A 52-week backfill is
about 24 MB. It never requests document.html, and a test asserts that.
Snapshot mode is a PREVIEW
watch_mode: false returns at most 25 records, hard-capped in code.
Watch semantics
First watch run seeds and emits zero deltas. A publication leaving the window is the window moving β a Bulletin week does not un-publish β and is never reported as a withdrawal. Any publication id that does not parse is counted and reported rather than silently dropped.
Terminal states
NORMAL Β· SUCCEEDED-0: GENUINE_EMPTY Β· SUCCEEDED-0 (no change) Β· PARTIAL Β· BLOCKED.
One delta type per Actor
This Actor watches correction-publication and nothing else. The other delta types in this family are separate Actors, each with its own price and its own baseline β so you pay for the feed you want and no other.
What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.
β° Optional: run it on a schedule
A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console β Schedules β Create new, add this actor with the watch-mode input above (watch_mode: true) so each run returns only the changes, and pick a cadence:
- Daily β
0 7 * * *(07:00 UTC): catch changes within a day. - Weekly β
0 7 * * 1: a Monday digest.
The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console β Integrations).
π° Pricing example
| Event | Free | Bronze | Silver | Gold |
|---|---|---|---|---|
Actor Start (apify-actor-start) | $0.02 | $0.02 | $0.02 | $0.02 |
Source check (source-check) | $0.10 | $0.09 | $0.08 | $0.067 |
EPO Publication Delta (epo-publication-delta) | $0.08 | $0.072 | $0.064 | $0.0536 |
Worked at the live Free-tier price (watch mode, one delta per change):
- 8 epo publication deltas: $0.02 start + $0.10 source check + 8 Γ $0.08 = $0.76
- 25 epo publication deltas: $0.02 start + $0.10 source check + 25 Γ $0.08 = $2.12
- 4000 epo publication deltas: $0.02 start + $0.10 source check + 4000 Γ $0.08 = $320.12
A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.
Yield on the sample run: PARTIAL: emitted 10 item(s); ITEM CAP REACHED: max_items (10) kept 10 of 32 matching publication(s). The rest are not in the baseline. Narrow delta_types or number_prefix, or raise max_items.. max_items is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.
βοΈ Legal & ToS
This actor reads public, logged-out pages and feeds published by data.epo.org. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.
β FAQ
Q: Do I need an API key or a login?
A: No. The source (data.epo.org) is read logged-out; the input schema has no key field and the actor carries no secrets.
Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event β retry later or narrow the input. A zero-row run bills the start fee plus one source check.
Q: How many rows can one run return?
A: Up to max_items (default 4000); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.
Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.
Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.
Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.
Q: How is this different from the other IP and trademark scrapers actors?
A: Same output shape and billing model; this one covers data.epo.org. The siblings under Related Actors cover the other sources or slices β run several on one schedule for a combined feed.
π Troubleshooting
- Run FAILED with BLOCKED β the source refused the request or changed its page shape β nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
- Status says CAPPED β your cap (
max_items) was reached β raise it for a bigger run. - Input validation error on start β a field is outside the schema's allowed values β start from the Quick start block and change one field at a time.
- Run TIMED-OUT β a very wide request on a slow day β raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
- First watch run shows no deltas β expected: it seeds the baseline; changes appear from the second run.
π Related Actors
- CIPO Trademarks Journal Scraper β Scrape the Canadian Trademarks Journal: advertised marks, applicants, goods and services, and status changes. Every run returns the current records aβ¦
- EPO Amended Patent Specifications Scraper β Scrape amended European patent specifications (B2/B3) from the EPO: patent, applicant, IPC and publication date. Every run returns the current recordβ¦
- EPO Patent Application Publications Scraper β Scrape published European patent applications (A1/A2) from the EPO: applicant, title, IPC and publication date. Every run returns the current recordsβ¦
- EPO Granted Patents Scraper β Scrape granted European patents (B1) from the EPO: proprietor, title, IPC and grant publication date. Every run returns the current records as a dataβ¦
- EPO European Patent Bulletin Scraper β Scrape the European Patent Bulletin: all publication kinds, applicant, title, IPC and publication date. Every run returns the current records as a daβ¦
- USPTO Trademark Official Gazette Scraper β Scrape the USPTO Trademark Official Gazette: marks, owners, classes, status and weekly changes. Every run returns the current records as a dataset. Oβ¦
- π’ About NexGen Watch β NexGen Watch is a catalog of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.
β Found this useful?
If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab β every one is read.
