Estonia Company Data — e-Business Register 🇪🇪

foXLabs European company-registry series: UK · France · Latvia · Czechia · Poland · Slovakia · Slovenia · Denmark · Norway · Finland

🎉 Turn the Estonian e-Business Register into clean, structured company data — no login, no API key, one row per entity, with the registry code, legal form, status, industry, address and (where published) email. Built for B2B sales, lead generation, KYB / compliance and market-research teams.

🔍 What is the Estonia Company Data — and when should you use it?

Give this actor company names or Estonian registry codes and it returns matching companies from the Estonian e-Business Register (open data) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: a company list for outreach; a quick profile before a call; or a starting point for account research.

Use something else when: you need revenue or headcount — the register carries identity, industry and contact fields, not financials.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/estonia-company-data.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull Estonia company records using the Apify Actor `foxlabs/estonia-company-data`.
Input: `searchQuery`, `registryCodes`, `legalForm`, `status` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"registryCodes":["12417834","10006966"],"maxResults":1000}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/estonia-company-data.md.

📋 Overview

Everything you need to turn the Estonian e-Business Register (open data) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole registry, one call — name or ID in, matching companies out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~estonia-company-data/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"registryCodes":["12417834","10006966"],"maxResults":1000}'

🚀 Getting Started (3 steps)

1. Choose your targets — company names or Estonian registry codes.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"registryCodes":["12417834","10006966"],"maxResults":1000}

Field	Type	Description
searchQuery	string	Find companies whose name contains this text (case-insensitive). Leave empty to browse by the filters below. Example: "Bolt" or "holding".
registryCodes	array	Look up specific companies by their 8-digit Estonian registry code (ariregistri kood). Overrides the name search. Example: ["12417834" = Bolt Technology OÜ,…
legalForm	string	Keep only companies of this legal form. "Any" returns all forms.
status	string	Which companies to include by registry status.
location	string	Keep only companies whose address contains this text — a county or city. Example: "Tallinn", "Harju", "Tartu". Leave empty for all of Estonia.
activityQuery	string	Keep only companies whose reported activity (EMTAK) matches — a numeric EMTAK code prefix (e.g. "62" for IT) or a keyword found in the activity text. Leave empty…
onlyWithEmail	boolean	Return only companies that publish a contact email (≈96% of active companies do). Useful for lead lists.
includeOwnership	boolean	Attach board members, shareholders and beneficial owners (UBO) to each company. Adds ~106 MB of reference downloads (≈2 GB unpacked) at the start of the run, so…
maxResults	integer	Maximum number of companies to return.

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
name	Name
registryCode	Registry Code
legalForm	Legal form / entity type
status	active / inactive / dissolved
email	Email
phone	Phone
county	County
primaryActivity	Primary Activity
registryUrl	Registry Url

💼 Use cases

1. Estonia B2B lead lists — active Estonian companies with an email where published. Input: name searches. Output: entities + industry + email. Use: a ready outreach list.

2. Firmographic enrichment — attach legal form and industry to a registry code. Input: registry codes. Output: the register record. Use: enrich a CRM.

3. KYB / due diligence — verify an Estonian company by registry code. Input: the code or name. Output: the canonical register record. Use: confirm existence and status.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/estonia-company-data').call({"registryCodes":["12417834","10006966"],"maxResults":1000});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/estonia-company-data').call(run_input={"registryCodes":["12417834","10006966"],"maxResults":1000})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads the Estonian e-Business Register (open data).

What do I search by? Company names or Estonian registry codes.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

Does it include an email? Where the register publishes one — Estonian entities commonly list a contact email.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResults, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads a public government business registry published as open data. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.27 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"registryCodes":["12417834","10006966"],"maxResults":1000}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from the Estonian e-Business Register (open data) by name or registry ID.