Slovakia Company Data — RPO Registry & SK NACE Activity
Pricing
$6.00 / 1,000 company records
Official Slovak company data from the register of financial statements: IČO, DIČ, legal form, SK NACE activity, registered address and accounting-unit records.
Why the actor went quiet. The RPO was transferred from the Statistical Office to the Ministry
of the Interior, and the old api.statistics.sk/rpo/v1 host stopped answering. Measured from four
different exits (home, Apify auto, datacenter, residential SK): the TLS handshake completes, the
request is sent, no response ever arrives, and the run waits until it times out. It is not an IP or
geography block — the host is gone for everyone. The last run that returned data was 2026-10-08.
What it reads now. The register publishes a complete bulk export under a CC-BY 4.0 licence: a full dump each month and a delta every night. That export is mirrored into a key-value store, sharded by the last three digits of the IČO, so an IČO lookup reads one ~330 KB shard instead of scanning a 900 MB dump. At run time the actor applies whatever daily deltas the register has published since the mirror was rebuilt, so the data stays one day behind the live register — the same lag the old REST API had, by the register's own documentation.
The data got richer, not poorer. The export carries fields the old search endpoint never
returned. New output fields: legalStatusCode (bankruptcy / liquidation entries),
sourceRegister, registrationOffice and registerFileNumber (which register holds the company,
which court keeps it, its file number there), signingRules (who may sign for the company, and
alone or jointly), officerDetails (each officer's role, start date and municipality as separate
fields, next to the existing flat officers list), businessActivities, esa2010,
municipalityCode, alternativeNames, organizationUnitCount and registerFlagsInconsistency.
Measured on 300 active companies: 25.3 of 33 fields filled on average, 19 fields at 100%, officers at 95%. On limited companies (s.r.o.), registered capital is filled on 96% and signing rules on 100%.
lastUpdatedInRegister is now always empty: the bulk export omits dbModificationDate, which
the old detail endpoint carried. Left empty rather than invented.sourceUrl points at the register's new home, https://rpo.minv.sk/new/.taxNumber, employees, website, email, phone and
district. The register does not carry them and the actor stopped emitting them in 0.1; only the
schema was still stale.company-record event per row, as before.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./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.capital, capitalCurrency (from the register's equities) and officers (the statutory body / managing directors).economicActivityDescription.taxNumber, employees, website, email, phone — the RPO does not carry them.