Finland Company Registry Scraper - PRH B2B Leads
Pricing
from $1.99 / 1,000 results
Finland Company Registry Scraper - PRH B2B Leads
Scrape PRH / YTJ open data — Finland's official company registry. Get business ID (Y-tunnus), company name, company form, main business line (NACE), address, website & registration date. Filter by name, location, company form & more. No login, no API key.
Pricing
from $1.99 / 1,000 results
Rating
0.0
(0)
Developer
Logiover
Maintained by CommunityActor stats
0
Bookmarked
6
Total users
1
Monthly active users
7 days ago
Last modified
Categories
Features
Share
Finland Company Registry Scraper — PRH / YTJ Open Data & Finnish B2B Leads (No API Key)
Pull a clean, structured list of Finnish companies straight from PRH / YTJ open data — the Finnish Patent and Registration Office (PRH) and the Business Information System (YTJ), Finland's official company registry. Filter by town, company form, industry (NACE) or registration date and get business ID (Y-tunnus), company name, company form, main business line, full address, website & registration date in tidy columns. Reads the open avoindata.prh.fi API directly — no login, no API key, no captcha.
🏆 Why this Finland company registry scraper?
17+ fields per company · tens of thousands of companies per run · direct official open-data API (no browser) · nested multi-language JSON flattened to clean English columns · export to JSON / CSV / Excel. The unofficial PRH / YTJ API alternative for Finnish B2B lead generation, prospecting and CRM enrichment.
✨ What this Actor does / Key features
- 🎯 Finland B2B lead data — business ID (Y-tunnus), current company name, company form, main line of business, full address, website and registration date, one clean row per company.
- 🔎 Rich filtering — search by company name, town/location, company form (OY, OYJ, AOY…), main business line (NACE / TOL code), postcode and registration-date range.
- 🆕 Find newly founded companies — filter by a registration-date window to surface Finnish businesses registered in that period.
- 🏢 Single-company lookup — resolve one company by its exact business ID (Y-tunnus) for CRM enrichment and KYC.
- 🌐 English-first flattening — the registry's deeply nested Finnish / Swedish / English JSON is flattened to clean columns, preferring English descriptions.
- 🔁 Auto-pagination & de-dupe — the API paginates ~100 companies per page; the Actor pages through automatically and de-dupes by business ID.
- 📦 Bulk export — tens of thousands of companies per query; export to JSON, CSV, Excel, HTML/XML or pull via the Apify API and webhooks.
- 🔓 No API key needed — reads the official open PRH / YTJ open data API; no registry account, no signup, no captcha.
🚀 Quick start (3 steps)
- Configure — set your filters (town, company form, main business line, dates, postcode) or just type a company
name. SetmaxResults. - Run — click Start. The Actor queries the PRH / YTJ open data API, paginates automatically and streams companies into your dataset.
- Get your data — open the Output tab and export to JSON, CSV, Excel or XML, or pull it via the Apify API.
📥 Input
Set at least one filter (or just a company name). Everything else is optional — combine a company form + town to assemble a large, targeted Finnish prospect list in a single run.
Example — limited companies (OY) in Helsinki
{"location": "Helsinki","companyForm": "OY","maxResults": 1000}
Example — software companies by NACE code (nationwide)
{"mainBusinessLine": "62010","maxResults": 2000}
Example — newly founded companies in 2025
{"registrationDateStart": "2025-01-01","registrationDateEnd": "2025-12-31","maxResults": 1000}
| Field | Type | Description |
|---|---|---|
name | string | Company name search (the API's name param), e.g. Nokia. A very broad name like oy can be slow — prefer location for big runs. |
location | string | Registered town, e.g. Helsinki (≈88,000 companies), Espoo, Tampere, Turku, Oulu, Vantaa. The most reliable high-volume filter. |
companyForm | string | Company form code: OY (limited company), OYJ (public limited), AOY (housing company), KY, AY, TMI… Leave empty for all. |
mainBusinessLine | string | Main line of business (NACE / TOL) code, e.g. 62010 (computer programming), 70220 (management consultancy), 73110 (advertising). |
postCode | string | Business-address postcode, e.g. 00100 (Helsinki centre), 33100 (Tampere). |
businessId | string | Exact business ID (Y-tunnus) for a single-company lookup, e.g. 0112038-9. Great for CRM enrichment. |
registrationDateStart / registrationDateEnd | string | Registration-date range (YYYY-MM-DD) — find newly founded firms. |
maxResults | integer | Stop after this many companies. Default 200, 0 = unlimited. |
useProxy | boolean | Route through Apify Proxy (datacenter). Default true — the open API is stable either way. |
proxyConfiguration | object | Apify Proxy override. Datacenter is plenty for the open PRH / YTJ API. |
Finding company-form & NACE codes: company-form codes include
OY,OYJ,AOY,KY,AY,TMI. Main-business-line (NACE / TOL) codes are numeric (e.g.62010software,73110advertising). You can also just search bynameorlocationand read thecompanyFormCode/mainBusinessLineCodecolumns in the output.
📤 Output
One clean row per company — flattened from the registry's nested multi-language JSON, exportable to JSON, CSV, Excel or XML. Here is a trimmed sample record:
{"businessId": "0100123-2","registrationDate": "1978-03-15","name": "Oy Emar Ab","companyFormCode": "16","companyForm": "Limited company","mainBusinessLineCode": "66190","mainBusinessLine": "Other activities auxiliary to financial services, except insurance and pension funding","street": null,"zip": "00131","city": "HELSINKI","addressType": "2","website": null,"lastModified": null,"source": "3","url": "https://tietopalvelu.ytj.fi/en/yritys/0100123-2","scrapedAt": "2026-07-06T00:00:00.000Z"}
💡 Use cases
- B2B lead generation — build targeted Finnish prospect lists by town + company form + industry, then push to your CRM.
- Sales prospecting — filter by company form and business line, and prioritize companies that registered a website.
- Market research — count and profile companies by NACE code, town and founding date to size a segment.
- KYC / compliance & due diligence — verify business IDs (Y-tunnus), company form and registration details from the official register.
- Competitor mapping — survey every company in a vertical or town in a single run.
- CRM enrichment — look companies up by business ID and append official registry fields.
👥 Who uses it
B2B sales & lead-gen teams · Finnish market researchers & analysts · KYC / compliance & AML teams · CRM & data-enrichment providers · fintech & credit-risk teams · agencies mapping the Finnish company landscape.
💰 Pricing
This Actor runs on a simple pay-per-result model — you pay for the companies you extract, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.
❓ Frequently Asked Questions
Is it legal to scrape PRH / YTJ? This Actor reads only the official open data that PRH publishes via its public open data API — no login or circumvention involved. As always, credit the source (PRH / YTJ) and follow PRH's terms and applicable law (such as GDPR) for your specific use case.
Does PRH / YTJ have a public API? Is this an API alternative?
Yes — the Finnish Patent and Registration Office (PRH) publishes the company registry as fully open, free JSON open data (avoindata.prh.fi/opendata-ytj-api). This Actor is the easiest PRH / YTJ open data alternative for non-developers: it queries that API with your filters, handles pagination, and flattens the nested multi-language JSON into clean English columns you can export directly.
Do I need an API key or a login? No. There is no PRH / YTJ account, login or API key required — only an Apify account. The open data API needs no key, signup or captcha.
How do I export Finnish company data to CSV or Excel?
Every run writes one row per company to a dataset. Set your filters, run, and use the Export button to download an .xlsx, .csv, JSON or XML file — or pull the data via the Apify API and webhooks.
How much data can I get? Tens of thousands of companies per query. Big towns return huge segments (Helsinki ≈ 88,000 companies). For very large segments, split your run by town, postcode or registration-date range and combine the datasets; the API paginates ~100 companies per page and the Actor pages through automatically.
Does it include company websites? It returns the website that each company registered with PRH / YTJ, when present. This comes straight from the official registry — but not every company (especially small or dormant firms) registers one, so the fill rate varies.
How do I find newly registered companies in Finland?
Set registrationDateStart (and optionally registrationDateEnd) to a date range and the scraper returns only Finnish companies registered in that window, straight from PRH / YTJ open data — ideal for catching newly founded firms early.
How do I get all limited companies (OY) in a Finnish city?
Combine location (for example Helsinki) with companyForm OY and raise maxResults to export a targeted list of Finnish limited companies with address and website.
Do I need a proxy?
No. The PRH / YTJ API is open, so you can turn useProxy off and go direct. Keeping Apify Proxy on (datacenter is plenty) is stable and recommended for large runs.
Which languages are the descriptions in?
PRH / YTJ data is published in Finnish, Swedish and English. This Actor flattens descriptions (company form, main business line) to English where available, falling back to the first available language.
🔗 More company registry & B2B data scrapers by logiover
Building a cross-border company dataset? Pair Finland with the rest of the official-registry suite:
| Country / registry | Actor |
|---|---|
| 🇸🇪 Sweden | Allabolag Scraper |
| 🇳🇴 Norway | Brreg Norway Company Scraper |
| 🇫🇷 France | France Company Registry Scraper |
| 🇨🇿 Czechia | Czech Company Registry Scraper |
| 🇦🇺 Australia | Australia Business Register Scraper |
| 🇬🇧 UK | UK Companies House Bulk Scraper |
| 🇺🇸 USA (NY) | USA New York Company Registry Scraper |
| 🌐 Global LEI | GLEIF LEI Scraper |
| 🇺🇸 SEC filings | SEC EDGAR Form D Scraper |
| 🌐 Trade data | Comtrade Trade Data Scraper |
👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.
⏰ Scheduling & integration
Schedule this Actor on Apify to refresh your Finnish company dataset daily or weekly — perfect for catching newly registered firms. Export results to JSON, CSV or Excel, sync to Google Sheets, or push to your CRM, database, BI tools and webhooks through the Apify API. Connect it to Make, n8n or Zapier to build automated lead-gen and enrichment pipelines.
🤖 AI Agents, MCP & RAG Integration
Finland Company Registry Scraper works natively as an on-demand data tool for AI assistants and autonomous workflows.
Connect this Actor directly to Apify AI, Claude Desktop, Cursor, VS Code, Windsurf, LangChain, or LlamaIndex via the official Apify MCP Server — no custom wrapper code needed:
{"mcpServers": {"apify": {"type": "http","url": "https://mcp.apify.com?tools=logiover/finland-company-registry-scraper"}}}
- Schema-typed inputs & outputs: Clean JSON records with explicit
.actor/input_schema.jsonand.actor/output_schema.jsondefinitions so LLM agents infer parameters and parse fields accurately without HTML noise. - Bounded & predictable runs: Built-in volume caps and pay-per-result budget guards prevent runaway agent tool loops.
- RAG & automation ready: Stream run datasets straight into vector stores, n8n, Make, Zapier, or webhook pipelines.
💬 Support, Issues & Reviews
- Bug reports & target-site changes: Hit an unexpected empty result or selector change? Open a ticket in the Issues tab with your Run ID or sample input — we actively monitor issues and ship fixes fast.
- Feature & field requests: Need an additional data attribute or filter? Request it in the Issues tab.
- Enjoying this Actor? If it saved you engineering time, please consider leaving an honest review on Apify Store or bookmarking logiover/finland-company-registry-scraper — organic developer feedback helps others discover reliable tools and keeps maintenance prioritized.
⚖️ Legal
This Actor reads only Finland's official open registry data (PRH / YTJ open data) and is intended for legitimate research, analytics and lead-generation use. You are responsible for complying with PRH's terms, GDPR and any applicable local laws, and for crediting the source (PRH / YTJ).
This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Finland Company Registry; Finland Company Registry and all other trademarks mentioned here are the property of their respective owners.
Finland scraping — frequently asked questions
Do I need a Finland API key, account or login?
No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.
How do I export Finland data to CSV, Excel, JSON or Google Sheets?
Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.
Can I schedule this Finland scraper to run daily or hourly?
Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the company records you care about really do change that fast.
How many company records can I get, and what does it cost?
See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.
Is scraping Finland legal?
This Actor collects only information that Finland publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.
What happens if Finland blocks the run or changes its layout?
A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".
Can I use this with an AI agent, LangChain or an MCP client?
Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.
📝 Changelog
2026-11-14
- Verified live high-volume benchmark (2026-11-14): extracted 650 structured records in 20.3s on the production build.
- Hardened internal proxy stall fallback and pay-per-event dataset instance budget protection.
2026-11-11
- Added reliable terminal run status telemetry and structured Apify AI / MCP Server (
mcp.apify.com) tool configuration. - Added direct Issues & Reviews support links and refreshed live maintenance verification.
2026-11-01
- Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
- README refreshed: 1 link to renamed Actors updated, 2 links to retired Actors removed; independence disclaimer added.
2026-10-15
- Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
- A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
- A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
- Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.
- The default used when the field is left out for
maxResultsis now 5,714 (was 200).
2026-09-23
- Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
- Output verified on a live run: 16 columns returned, 94.8% of cells populated.
- Run reliability reviewed: 100.0% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.
2026-09-01
- Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
- Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
- No change to input, output fields or scraping logic.
2026-08-01
- Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
- Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.
2026-07-06
- ✨ README overhaul: richer output sample, ready-to-run example scenarios, cross-promo links to the company-registry suite, and a clearer quick-start.
2026-07-01
- Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
- Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
- Added ready-to-run example tasks that cover common real-world use cases.
2026-06-15
- Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.
*Maintained: last verified 2026-11-14 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).