🔎 Finland Trade Register Filing Events

One registry_record per PUBLIC NOTICE ROW (a trade-register filing event) on the official PRH open-data registered-notices API, filtered by a notice-date window (noticeRegistrationDateStart/End — July 2026 = 38,355 companies with a notice in-window). Company Business ID + name and the notice's record number, type of registration, entry codes and registration date are carried verbatim. This is the date-windowed filing-EVENT stream — a different job from the finland-prh-ytj-company-registry roster (the full company master) and the finland-prh-business-filing-lookup single-entity check.

One structured registry_record per record from proven public sources, logged-out. Public, robots-honoured.

Output is one fi_trade_register_notice row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: avoindata.prh.fi.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

Who buys this

Buyers usually search for Finland trade register or Finnish business register.

• Sales and lead-generation teams building lists from Finland trade register.
• KYB, onboarding and compliance teams checking Finnish business register.
• Market researchers and data teams that need the official record as rows.

📊 Sample Output

Real rows from run XH3alG2KVWhtPFfft on build 0.1.17 (2026-09-23), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

business_id	company_name	notice_registration_date	record_number	notice_window_start	notice_window_end
0100036-0	Askolan Kotolämpö Oy	2026-09-10	2026/61205W	2026-08-23	2026-09-23
0100123-2	Oy Emar Ab	2026-09-02	2026/03921I	2026-08-23	2026-09-23
0100123-2	Oy Emar Ab	2026-09-02	2026/03921G	2026-08-23	2026-09-23
0100320-3	Kiinteistö Oy Sammatin Jermula	2026-08-29	2026/59067T	2026-08-23	2026-09-23
0100435-3	Esbogård Aktiebolag	2026-08-27	2026/03849F	2026-08-23	2026-09-23
0100435-3	Esbogård Aktiebolag	2026-08-27	2026/438928	2026-08-23	2026-09-23
0100537-2	Gumbölen Ratsastuskeskus Oy	2026-09-21	2026/468541	2026-08-23	2026-09-23
0100537-2	Gumbölen Ratsastuskeskus Oy	2026-09-21	2026/468530	2026-08-23	2026-09-23

The run finished with the status message: NORMAL: 10 unique rows (0 duplicates collapsed) from 2026-09-23. billable=10 [requested_cap=None, delivered=10]

✅ 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_type (string) — e.g. fi_trade_register_notice
• business_id (string/null) — e.g. 0100036-0
• company_name (string/null) — e.g. Askolan Kotolämpö Oy
• notice_registration_date (string/null) — e.g. 2026-09-10
• record_number (string/null) — e.g. 2026/61205W
• type_of_registration (string/null) — e.g. TA
• entry_codes (string/null) — e.g. TASE
• trade_register_status (string/null) — e.g. 1
• notice_window_start (string/null) — e.g. 2026-08-23
• notice_window_end (string/null) — e.g. 2026-09-23
• source (string/null) — e.g. finland-trade-register-filing-events
• release_date (string/null) — e.g. 2026-09-23
• source_url (string/null) — e.g. https://avoindata.prh.fi/opendata-registerednotices-api/v3/
• observed_at (string/null) — e.g. 2026-09-23T16:10:12Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row
• license (string/integer/null) — null in every sample row
• attribution (string/integer/null) — null in every sample row

✅ What you get

• record_type (string) — e.g. fi_trade_register_notice
• business_id (string/null) — e.g. 0100036-0
• company_name (string/null) — e.g. Askolan Kotolämpö Oy
• notice_registration_date (string/null) — e.g. 2026-09-10
• record_number (string/null) — e.g. 2026/61205W
• type_of_registration (string/null) — e.g. TA
• entry_codes (string/null) — e.g. TASE
• trade_register_status (string/null) — e.g. 1
• notice_window_start (string/null) — e.g. 2026-08-17
• notice_window_end (string/null) — e.g. 2026-09-17
• source (string/null) — e.g. finland-trade-register-filing-events
• release_date (string/null) — e.g. 2026-09-17
• source_url (string/null) — e.g. https://avoindata.prh.fi/opendata-registerednotices-api/v3/
• observed_at (string/null) — e.g. 2026-09-17T17:19:50Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row
• license (string/integer/null) — null in every sample row
• attribution (string/integer/null) — null in every sample row

What you get

One registry_record per entity/notice, deduplicated on the source-native id. Fields the sources do not publish are honest null. A run_receipt row carries the source URLs, scope, reconciliation counts, and delivered/duplicate totals.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "maxRecords": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 10 × $0.02 registry_record = $0.22 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
  "maxRecords": 5000
}

Up to 5000 rows (the schema default for maxRecords) — about $100.02 on the Free tier ($0.02 start + 5000 × $0.02) if the source has that many.

4. A filtered run

{
  "maxRecords": 10,
  "fieldMatch": {
    "company_name": "Askolan Kotolämpö Oy"
  }
}

Keeps only rows whose company_name contains Askolan Kotolämpö Oy (a value from the sample run above), matched case-insensitively after the source is read and before the maxRecords cap, so the cap counts matches and only delivered matches are billed. searchText does the same across every column. Zero matches end the run as EMPTY_SELECTION with no row charged — if the source has moved on since that sample run, pick a value you see in your own first run. The source is still read in full — this narrows what you receive and pay for, not what the source serves.

🧾 JSON sample record

One real record from run XH3alG2KVWhtPFfft, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "fi_trade_register_notice",
  "business_id": "0100036-0",
  "company_name": "Askolan Kotolämpö Oy",
  "notice_registration_date": "2026-09-10",
  "record_number": "2026/61205W",
  "type_of_registration": "TA",
  "entry_codes": "TASE",
  "trade_register_status": "1",
  "notice_window_start": "2026-08-23",
  "notice_window_end": "2026-09-23",
  "source": "finland-trade-register-filing-events",
  "release_date": "2026-09-23",
  "source_url": "https://avoindata.prh.fi/opendata-registerednotices-api/v3/",
  "observed_at": "2026-09-23T16:10:12Z"
}

🔧 How it works

Source. The actor reads avoindata.prh.fi — endpoints: https://avoindata.prh.fi/opendata-registerednotices-api/v3/. 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. Pacing: CRAWL_DELAY=0.0.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

How it behaves

Companies with a public notice in the requested window are paged 50/page from the PRH registered-notices API; each company's public-notice rows dated in the window are expanded to one record each, deduped on Business ID + record number + date. Notice fields are carried verbatim. count reconciled against the API's totalResults (companies-in-window). Streaming, bounded to maxRecords; memory bounded.

Attribution

Contains data from the Finnish Patent and Registration Office (PRH), reused under the PRH open-data licence. Each run_receipt and the actor README carry this attribution.

Source

https://avoindata.prh.fi/opendata-registerednotices-api/v3/

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Registry Record (registry_record)	$0.02	$0.018	$0.016	$0.0134

Worked at the live Free-tier price:

• 8 registry records: $0.02 start + 8 × $0.02 = $0.18
• 25 registry records: $0.02 start + 25 × $0.02 = $0.52
• 5000 registry records: $0.02 start + 5000 × $0.02 = $100.02

A run that delivers zero rows charges the $0.02 start fee only. 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: NORMAL: 10 unique rows (0 duplicates collapsed) from 2026-09-23. billable=10 [requested_cap=None, delivered=10]. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by avoindata.prh.fi. 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 (avoindata.prh.fi) 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; 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 only.

Q: How many rows can one run return?
A: Up to maxRecords (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. 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 company registry checks actors?
A: Same output shape and billing model; this one covers avoindata.prh.fi. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source (CRAWL_DELAY=0.0) and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 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 (maxRecords) 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.

🔗 Related Actors

• EU VAT Validator — VIES per-answer check — Validate EU VAT numbers against the official EU VIES service — one verdict per number with the registered name and date. No API key; pay per complete…
• Finland PRH Business Filing Lookup — A per-identity check: submit identifiers, get one official answer each. Billed per completed official resolution — a not-found, ambiguous, or unavail…
• Finland PRH YTJ Company Registry — One record per Finnish company from the official PRH open-data YTJ API v3 (business ID, current name, legal form, main business line, primary address…
• FMCSA Motor Carrier Authority Check — A per-identity check: submit identifiers, get one official answer each. Billed per completed official answer — an unresolved, ambiguous, or unavailab…
• Singapore MAS Financial Institutions Directory Scraper — Scrape the MAS Financial Institutions Directory: licensed entities, licence type, status and changes. Every run returns the current records as a data…
• New York Active Corporation Check — A per-identity check: submit identifiers, get one official answer each. Billed per completed official answer — an unresolved, ambiguous, or unavailab…
• 🏢 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.