Slovakia Company Data — RPO Register of Legal Entities 🇸🇰

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

🎉 Turn the Slovak business register into clean, structured company data — no login, no API key, one row per entity, with legal form, industry, the statutory body (directors) and registered capital. Built for B2B sales, lead generation, KYB / compliance and market-research teams.

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

Give this actor company names or Slovak IČO numbers and it returns matching companies from the Slovak Register of Legal Entities (RPO, the Ministry of the Interior’s official open-data export) — as clean, deduplicated rows you can filter, export or feed to an AI agent. The register publishes a complete export every night; each run reads the newest one, so rows are as current as the register itself makes them.

Use it when you need: a Slovakia company list for outreach; formation / status monitoring; or a canonical registry record for KYB and due diligence.

Use something else when: you need firmographics the registry doesn’t hold (revenue, headcount, website, email) — pair this with an enrichment actor from Fox Labs.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/slovakia-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 Slovakia company records using the Apify Actor `foxlabs/slovakia-company-data`.
Input: `queries` is a list of company names or Slovak IČO numbers. `maxResultsPerQuery` caps rows per query.
Start with: {"queries":["ESET","31333532"],"maxResultsPerQuery":50}
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/slovakia-company-data.md.

📋 Overview

Everything you need to turn the Slovak Register of Legal Entities (RPO, the Ministry of the Interior’s official CC-BY open-data export) 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 join key — registrationNumber ties rows across runs and to other Fox Labs actors.
• 💰 Pay only for results — per-row pricing, empty/failed lookups never billed.
• 🤖 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~slovakia-company-data/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["ESET","31333532"],"maxResultsPerQuery":50}'

🚀 Getting Started (3 steps)

1. Choose your targets — company names or Slovak IČO numbers.
2. Set the cap — maxResultsPerQuery limits rows per query.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"queries":["ESET","31333532"],"maxResultsPerQuery":50}

Field	Type	Description
queries	array	Company names or Slovak IČO numbers.
maxResultsPerQuery	integer	Caps rows per query.
maxConcurrency	integer	How many queries to fetch at once.
includeRaw	boolean	Attach the source’s untouched record under raw.

📤 Output

One row per company, saved to the dataset. Every row also carries query, scrapedAt, and — when a lookup fails — an error explaining why (never silently dropped, never billed).

Field	Description
country	Country
registry	Registry
companyName	Company / entity name
registrationNumber	Registry ID — the join key
status	active / inactive / dissolved
statusRaw	Status exactly as the registry words it
legalForm	Legal form / entity type
incorporatedOn	Formation / registration date (ISO)
dissolvedOn	Dissolution date where applicable (ISO)
address	Principal address
city	City
postalCode	Postal code
countryName	Country
industry	Primary industry (NACE)
industryCode	Primary industry code (NACE)
capital	Registered share capital
officers	Officers
sourceUrl	Public registry URL for the record
legalFormCode	Legal-form code
capitalCurrency	Share-capital currency
previousNames	Historical names
internalId	Internal Id
legalStatusCode	Insolvency / liquidation code — empty means the register holds no such entry
sourceRegister	Which register holds the company (commercial register, trade register, associations…)
registrationOffice	The office or court that keeps the record
registerFileNumber	The company’s file number in that register (e.g. Sa/121/P)
signingRules	Who may sign for the company, and alone or jointly
officerDetails	Each officer as role, start date and municipality, next to the flat officers list
businessActivities	Registered business activities
esa2010	ESA 2010 institutional-sector classification
municipalityCode	Municipality code (LAU)
alternativeNames	Trading / alternative names
organizationUnitCount	Number of registered branches or establishments
registerFlagsInconsistency	The register itself flags this record as inconsistent

💼 Use cases

1. Slovakia B2B lead lists — active Slovak companies with directors and capital. Input: name searches. Output: entities + officers + capital. Use: a ready sales list.

2. Ownership & governance — read the statutory body (Konateľ) and registered capital. Input: IČO or name. Output: officers + capital. Use: map decision-makers.

3. KYB / due diligence — verify a Slovak entity by IČO. Input: the IČO or exact name. Output: the canonical register record. Use: confirm existence, form and capital.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/slovakia-company-data').call({"queries":["ESET","31333532"],"maxResultsPerQuery":50});
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/slovakia-company-data').call(run_input={"queries":["ESET","31333532"],"maxResultsPerQuery":50})
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

Written for apify-client 3 for Python, where call() returns a run object; with version 1 or 2 it returns a dict — write run['defaultDatasetId'] there.

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your queries → 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 Slovak Register of Legal Entities (RPO) from the Ministry of the Interior’s official open-data export, licensed CC-BY 4.0.

What do I search by? Company names or Slovak IČO numbers.

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

Why are firmographics like revenue or website missing? A public business registry doesn’t hold them; we don’t ship empty columns. Pair with an enrichment actor from Fox Labs.

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

🐛 Troubleshooting

• Fewer rows than expected — raise maxResultsPerQuery, or refine the name.
• 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 registered agent’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.15 — 2026-10-25 — the register moved, and the data came back richer

• The RPO was transferred from the Statistical Office to the Ministry of the Interior and the old api.statistics.sk host stopped answering — measured from four different exits, so it is not a block but an end of service. The actor now reads the register’s own bulk export, published under a CC-BY 4.0 licence, and applies the register’s nightly deltas on top of it at run time.
• Twelve new fields, none of the old ones removed: legalStatusCode (insolvency / liquidation entries), sourceRegister, registrationOffice and registerFileNumber, signingRules (who may sign for the company, alone or jointly), officerDetails, businessActivities, esa2010, municipalityCode, alternativeNames, organizationUnitCount, registerFlagsInconsistency.
• Measured on 300 active companies: 25.3 of 33 fields filled on average, 19 fields at 100%, officers at 95%; on limited companies registered capital is filled on 96%.
• lastUpdatedInRegister is now always empty — the bulk export omits it. Left empty rather than invented.
• No pricing change: one company-record event per row.

0.1.14 — 2026-10-08 — README: the Python example works with the current Apify client

• The README's Python example read the results with run['defaultDatasetId']. With the current Apify client for Python (version 3) call() returns a run object, not a dict, and that line raised TypeError: 'Run' object is not subscriptable — after the run itself had finished. The example now reads run.default_dataset_id; with client version 1 or 2, keep run['defaultDatasetId']. Checked with apify-client 3.2.1, 2.5.1 and 1.12.2.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Fetch the entity detail — the actor is no longer near-empty. The RPO /search endpoint returns only identity + address, so legal form, industry, establishment date and officers came back blank. Added a per-entity /entity/{id} detail call, recovering legalForm, legalFormCode, incorporatedOn, industry, district.
• Recovered registered capital + officers. Added capital, capitalCurrency (from the register's equities) and officers (the statutory body / managing directors).
• Fixed the industry mapping to read economicActivityDescription.
• Dropped empty-promise columns taxNumber, employees, website, email, phone — the RPO does not carry them.
• README rebuilt to the full standard.