# Estonia Company Register — Äriregister Lookup (`sourcerow/estonia-company-register`) Actor

Look up any of 376,000 Estonian companies by name or registry code — legal form, VAT number, registration status and address, from the official Äriregister open data.

- **URL**: https://apify.com/sourcerow/estonia-company-register.md
- **Developed by:** [SourceRow](https://apify.com/sourcerow) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 company resolveds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

Look up any of Estonia's 376,000 registered companies by name or registry code.
Legal form, VAT number, registration status and address, resolved against the
complete register rather than the first page of search results.

### What it does

The Estonian Business Register publishes its full company file as open data.
This Actor downloads it at the start of every run — 18 MB, about four seconds —
indexes it, and resolves every query against the complete file. One row per
query, 25 fields on every row.

Because the whole register is in memory, a name search reports how many
companies matched, not just the first one. `total_matches` above 1 means the
query was ambiguous.

### What you get

25 fields per row, including `registry_code`, `name`, `legal_form`,
`vat_number`, `status`, `is_registered`, `first_registered_on`, `region`,
`total_matches`, `name_match_score` and `matched_by`.

The table view shows 13 of them; all 25 are in the JSON, CSV and Excel
downloads.

### Input

| Field | Meaning |
|---|---|
| `registryCodes` | Estonian registry codes, exact lookups. |
| `names` | Company names to search. |
| `queriesText` | A pasted list of either, one per line. |
| `maxCompanies` | Stop after this many. `0` removes the cap. |

```json
{
  "registryCodes": ["14056464", "17449106"],
  "maxCompanies": 100
}
```

### Sample output

One complete record:

```json
{
  "query": "14056464",
  "matched_by": "registry_code",
  "name_match_score": null,
  "registry_code": "14056464",
  "name": "Bolt Holdings OÜ",
  "legal_form": "Osaühing",
  "vat_number": "EE102684528",
  "status": "Registrisse kantud",
  "is_registered": true,
  "first_registered_on": "2016-05-27",
  "region": "Kesklinna linnaosa, Tallinn, Harju maakond",
  "total_matches": 1,
  "issues": ""
}
```

### Pricing

| Event | Per 1,000 | Notes |
|---|---|---|
| Company resolved | $4.00 | Queries that find nothing are not charged |

There is no start fee and no per-row dataset fee. The register is published as a
single file and there is no per-company search endpoint, so the whole 18 MB is
downloaded on every run. That is what makes the first answer take a few seconds
and every answer after it instant, and it is why this Actor can report
`total_matches` — the number of companies a name actually matched — which a
paginated search could not.

### What it does not do

**`legal_form` and `status` are in Estonian.** The register publishes them that
way and they are passed through unchanged rather than translated.
`Osaühing` is a private limited company, `Aktsiaselts` a public one,
`Registrisse kantud` means entered in the register. `is_registered` is the
boolean if that is all you need.

**No financials, no officers, no ownership.** The open data file covers company
identity and status. Annual reports and board members are behind the Estonian
register's own paid services.

**A name is not a unique key.** Name searches return the best match and report
`total_matches`. Anything above 1 needs a human decision.

**The register is a snapshot per run.** The file is downloaded fresh at the
start of each run, so data is as current as the last publication, not to the
minute.

### Notes

Batch the lookups. The register is downloaded once per run whatever you ask
for, so one run of 500 codes takes about as long as one run of one.

Sort by `name_match_score` ascending and check the bottom of the list first.
That is where wrong matches are.

`not_currently_registered` means the company is in the file but no longer
active. That is still worth knowing.

`vat_number` can be fed straight into a VIES check to confirm the company is
trading across EU borders.

### Support

Open the **Issues** tab with the exact query and the `matched_by`,
`total_matches` and `issues` values from the row.

### Licence and attribution

Company data from the Estonian Business Register (Äriregister), published as
open data by the Centre of Registers and Information Systems (RIK). RIK does not
endorse this Actor.

# Actor input Schema

## `registryCodes` (type: `array`):

Eight-digit Estonian registry codes.

## `names` (type: `array`):

Company names to search across all 376,000 companies, not just the first page.

## `queriesText` (type: `string`):

Paste a list here instead. Mixed is fine.

## `maxCompanies` (type: `integer`):

Stop after this many. **0 removes the cap.**

## Actor input object example

```json
{
  "registryCodes": [
    "14056464",
    "17449106"
  ],
  "names": [],
  "maxCompanies": 100
}
```

# Actor output Schema

## `companies` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "registryCodes": [
        "14056464",
        "17449106"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sourcerow/estonia-company-register").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "registryCodes": [
        "14056464",
        "17449106",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sourcerow/estonia-company-register").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "registryCodes": [
    "14056464",
    "17449106"
  ]
}' |
apify call sourcerow/estonia-company-register --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sourcerow/estonia-company-register"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/H5pfwmNFtTAXzhGWP/builds/dl27xuaV6xedlFyaI/openapi.json