Estonia Business Register Scraper — Äriregister Company Data avatar

Estonia Business Register Scraper — Äriregister Company Data

Pricing

$5.00 / 1,000 results

Go to Apify Store
Estonia Business Register Scraper — Äriregister Company Data

Estonia Business Register Scraper — Äriregister Company Data

Scrape any company in Estonia from the Äriregister (Estonian Business Register) by registry code — legal name, registry code, status, VAT, board & representation, shareholders, beneficial owners and annual reports. Structured JSON, no API key. You pay per completed lookup — matched or not.

Pricing

$5.00 / 1,000 results

Rating

0.0

(0)

Developer

NeuralVerge

NeuralVerge

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Estonia Business Register Scraper — Äriregister Company Data ✅ No API Key

Scrape any Estonian Äriregister (Business Register) company profile from its registry code — legal name, registry code, legal form, status, address, VAT, board & right of representation, shareholders, beneficial owners (UBOs), areas of activity, annual reports and documents. Powered by the Neuralverge API. No API key or account required, and you pay per completed lookup — matched or not; failed runs are never charged.

Ideal for KYC/KYB, due diligence, compliance, lead enrichment and feeding company data to AI agents.

✨ Why this Actor

  • 🇪🇪 Full Äriregister profile — identity, VAT, representation, shareholders, UBOs, activities, annual reports and documents in one structured object.
  • 💸 Pay per completed lookup — matched or not. An unresolved registry code comes back as one no result row, billed like any other row, so a batch never silently loses an input. A run that fails is never charged.
  • 🔑 No API key or account — extraction runs on the Neuralverge backend.
  • Real-time & structured — fresh data each run and one predictable JSON schema, ready for a spreadsheet, database, CRM or AI pipeline.

🔧 How it works

  1. Provide an Estonian registry code (e.g. 11995440) — or an advanced full Äriregister profile URL.
  2. Run the Actor. The heavy lifting — fetching and AI-structuring the profile — happens on the Neuralverge backend.
  3. Get one flat dataset row per company — 24 columns, all at the top level (url, companyName, registryCode, legalForm, status, address, …). Export to CSV, JSON or Excel, or pull it over the Apify API.

If the company can't be resolved, the run still delivers one explicit no result row instead of finishing empty — it is billed like any other row. A run that fails (missing input, bad key, upstream error) writes nothing and costs $0.00.

Input

One company per run.

FieldTypeNotes
companyNumberstringThe Estonian registry code (registrikood), e.g. 11995440.
companyUrlstringAdvanced: a full Äriregister profile URL to use instead of the code.
{
"companyNumber": "11995440"
}

What you'll receive

One flat row per company. Every field sits at the top level of the row, so the Output tab shows a single table with all 24 columns — there are no views to switch between. Exports (CSV, JSON, XML, Excel) contain exactly the same fields.

Columns: url, companyName, registryCode, legalForm, status, address, vatNumber, vatRegistrationDate, taxDebtStatus, taxLastCheckedDate, articlesOfAssociationEffectiveDate, articlesOfAssociationDocumentUrl, registryCardUrl, registryCardLastEntryDate, shareCapital, financialYear.

ListsrightOfRepresentation, contacts, shareholders, areasOfActivity, annualReports, beneficialOwners, procedureInformation, documents — come back as arrays. The table renders each as an expandable "N items" cell; a CSV/JSON/Excel export carries them in full.

Nulls are normal. The column set is the same on every run, so a field the source does not expose for this company comes back null rather than disappearing — a spreadsheet or CRM mapping built on one run keeps working on the next.

When nothing is found

A lookup that runs but matches nothing still returns a row, so a batch never silently loses an input:

ColumnValue
urlthe Äriregister profile URL that was looked up
foundfalse
messagewhy nothing was returned

Filter these out with found != false (or drop rows where message is set). This row is billed as one company — see Pricing.

Example output (real run)

A real dataset row, shown in full.

{
"url": "https://ariregister.rik.ee/eng/company/11995440",
"companyName": "Digital Revolution OÜ",
"registryCode": "11995440",
"legalForm": "Private limited company",
"status": "Entered into the register",
"address": "Harju maakond, Tallinn, Haabersti linnaosa, Paldiski mnt 227-105, 13520",
"vatNumber": "EE101397641",
"vatRegistrationDate": "01.10.2010",
"rightOfRepresentation": [
{
"name": "Iris Rõngelep",
"personalCode": "47503050311",
"role": "Management board member"
}
],
"contacts": [
{
"type": "E-mail address",
"value": "[[email protected]](/cdn-cgi/l/email-protection)"
}
],
"shareholders": [
{
"name": "OÜ Justkull",
"identifier": "11059321",
"stakePercentage": 100
}
],
"taxDebtStatus": null,
"taxLastCheckedDate": null,
"areasOfActivity": [
{
"code": "64201",
"description": "Activities of holding companies",
"isPrimary": true
}
],
"annualReports": [
{
"period": "01.01.2025 - 31.12.2025",
"submittedDate": "27.06.2026",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9014311788?document_type=ddoc"
},
{
"period": "01.01.2024 - 31.12.2024",
"submittedDate": "28.06.2025",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9013098123?document_type=ddoc"
},
{
"period": "01.01.2023 - 31.12.2023",
"submittedDate": "09.08.2024",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9011968181?document_type=ddoc"
},
{
"period": "01.01.2022 - 31.12.2022",
"submittedDate": "09.08.2024",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9011968162?document_type=ddoc"
},
{
"period": "01.01.2021 - 31.12.2021",
"submittedDate": "09.08.2024",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9011968137?document_type=ddoc"
},
{
"period": "01.01.2020 - 31.12.2020",
"submittedDate": "09.08.2024",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9011968053?document_type=ddoc"
},
{
"period": "01.01.2019 - 31.12.2019",
"submittedDate": "06.09.2020",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9007208002?document_type=ddoc"
},
{
"period": "01.01.2018 - 31.12.2018",
"submittedDate": "17.09.2019",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9006435424?document_type=ddoc"
},
{
"period": "01.01.2017 - 31.12.2017",
"submittedDate": "11.06.2018",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9005218266?document_type=ddoc"
},
{
"period": "01.01.2016 - 31.12.2016",
"submittedDate": "10.11.2017",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9004722038?document_type=ddoc"
},
{
"period": "01.01.2016 - 31.12.2016",
"submittedDate": "03.08.2017",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9004543771?document_type=ddoc"
},
{
"period": "01.01.2015 - 31.12.2015",
"submittedDate": "03.08.2017",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9004543712?document_type=ddoc"
},
{
"period": "01.01.2014 - 31.12.2014",
"submittedDate": "30.06.2015",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9002717778?document_type=ddoc"
},
{
"period": "01.01.2013 - 31.12.2013",
"submittedDate": "27.06.2014",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9001720109?document_type=ddoc"
},
{
"period": "01.01.2012 - 31.12.2012",
"submittedDate": "19.08.2013",
"documentUrl": "https://ariregister.rik.ee/eng/company/11995440/file/9001150640?document_type=ddoc"
},
{
"period": "01.01.2011 - 31.12.2011",
"submittedDate": "26.06.2012",
"documentUrl": null
}
],
"beneficialOwners": [
{
"name": "Erko Kundla",
"personalCode": "36612030253",
"countryOfResidence": "Estonia"
}
],
"articlesOfAssociationEffectiveDate": "25.10.2017",
"articlesOfAssociationDocumentUrl": null,
"registryCardUrl": null,
"registryCardLastEntryDate": "21.09.2010",
"shareCapital": "5 000 €",
"financialYear": "01.01 - 31.12",
"procedureInformation": [
{
"entryNumber": null,
"entryDate": "21.09.2010",
"description": "Entered into the register"
}
],
"documents": [
{
"title": "Articles of association",
"date": "25.10.2017",
"url": "https://ariregister.rik.ee/eng/company/11995440/file/9004722038?document_type=ddoc"
},
{
"title": "Articles of association",
"date": "21.09.2010",
"url": "https://ariregister.rik.ee/eng/company/11995440/file/9004543771?document_type=ddoc"
}
]
}

Pricing

Pay per event — $0.005 per company ($5 per 1,000) written to the dataset. There is no run fee and no start fee.

EventPriceCharged
Actor startfreenever
Failed run — invalid input, API error, timeoutfreenever
Row written to the dataset$0.005 ($5 / 1,000)every row, including the "no result" row

A completed lookup is billed as one company, matched or not. When the source returns nothing, the Actor writes one explicit no-result row — the query you submitted plus found: false and a message explaining it — and that row is charged at the normal per-company price. A run that fails (missing input, bad key, upstream error) writes no row and costs $0.00.

Pricing is on top of your Apify platform usage.

Rate limit

Every Neuralverge Actor talks to the same backend, so there is a ceiling on how fast one Apify account can pull from it: 5 requests per second, counted across all Neuralverge Actors together. One run is normally one request, so this is about how many runs you start at once, not about the size of a single run — 5 requests per second is roughly 30 runs in flight at the same time, which is well above ordinary use.

Above the ceiling the backend answers HTTP 429. The Actor waits out the Retry-After it asks for and retries a few times before giving up; a run that does give up writes no row and is not charged.

If you need a higher rate for a bulk job, get in touch.

Free plan limits

Users on any paid Apify plan are not affected by anything in this section.

On the Apify Free plan all Neuralverge Actors share one budget, per user and per calendar month: 15 runs in total, at most 5 of them on this Actor, and 35 returned rows. A run that finds nothing still counts, because the lookup is performed either way. LinkedIn People Search is metered differently — one run there uses 25 of the 35 rows, because a full page of 25 profiles is bought upstream whether or not all of them are returned. When a limit is reached the Actor stops gracefully with a status message naming it; everything resets on the 1st of every month, and any paid Apify plan removes all of it.

Integrations & API

Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client.

FAQ

Do I need an account or API key? No. Extraction runs on the Neuralverge backend.

What identifier do I use? The Estonian registry code (registrikood) — an 8-digit number like 11995440. You can also pass a full Äriregister profile URL.

Am I charged if a company isn't found? Yes — a lookup that ran is billed as one company even when it matched nothing; you get a no result row that says so. A run that fails (missing input, bad key, upstream error) is not charged.


Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the Republic of Estonia or the Centre of Registers and Information Systems (RIK). Data originates from the public Äriregister.