🔔 Slovakia Public-Sector Partners Register

One record per registered public-sector partner from the official RPVS OData — official ID, business name, validity dates, and beneficial owners when expanded. Honest scope: the public-sector-partners register, NOT a full company roster.

Public, robots-honoured, keyless.

Output is one sk_public_sector_partner row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: rpvs.gov.sk.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run jn4Cn6xAQ5e0cZna1 on build 0.1.6 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

partner_id	vlozka_number	ico	business_name	person_form	valid_from
1	1	44543832	LITOGRAF s. r. o.	PravnickaOsoba	2017-02-01T00:00:00+01:00
2	2	36742023	JUDr. Radovan Repa, advokát, s. r. o.	PravnickaOsoba	2017-02-01T00:00:00+01:00
3	3	47559870	ZELEX, s.r.o.	PravnickaOsoba	2017-02-01T00:00:00+01:00
4	4	36823457	FECOM ICT s.r.o.	PravnickaOsoba	2017-02-01T00:00:00+01:00
5	5	44562977	GPP INDUSTRIE BAU, s. r. o.	PravnickaOsoba	2017-08-03T00:00:00+02:00
6	6	48175013	4bigdata spol. s r.o.	PravnickaOsoba	2017-02-01T00:00:00+01:00
7	7	41549708	Viliam Štafurik - RENTON	PravnickaOsoba	2017-02-01T00:00:00+01:00
8	8	43216731	Ing. Pavol Sebök PAULOS - DLS	PravnickaOsoba	2017-02-01T00:00:00+01:00

The run finished with the status message: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. sk_public_sector_partner
• partner_id (integer/null) — e.g. 1
• vlozka_number (integer/null) — e.g. 1
• ico (string/null) — e.g. 44543832
• business_name (string/null) — e.g. LITOGRAF s. r. o.
• person_name (string/null) — null in every sample row
• person_form (string/null) — e.g. PravnickaOsoba
• valid_from (string/null) — e.g. 2017-02-01T00:00:00+01:00
• valid_to (string/null) — e.g. 2017-09-25T00:00:00+02:00
• detail_record_count (integer/null) — e.g. 1
• beneficial_owner_count (integer/null) — e.g. 2
• beneficial_owners (array/null) — e.g. [{"name": "Jaroslav Vidra", "is_public_official": true, "valid_from": "2017-02-0
• source (string/null) — e.g. slovakia-public-sector-partners
• release_date (string/null) — null in every sample row
• source_url (string/null) — e.g. https://rpvs.gov.sk/opendatav2/Partneri?$expand=PartneriVerejnehoSektora,Konecni
• observed_at (string/null) — e.g. 2026-09-18T06:17:38Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, reconciliation counts, and delivered/duplicate totals.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "maxRecords": 50,
  "maxPages": 5
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.02 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "maxRecords": 5,
  "maxPages": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
  "maxRecords": 2000,
  "maxPages": 5
}

Up to 2000 rows (the schema default for maxRecords) — about $40.02 on the Free tier ($0.02 start + 2000 × $0.02) if the source has that many.

🧾 JSON sample record

One real record from run jn4Cn6xAQ5e0cZna1, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "sk_public_sector_partner",
  "partner_id": 1,
  "vlozka_number": 1,
  "ico": "44543832",
  "business_name": "LITOGRAF s. r. o.",
  "person_name": null,
  "person_form": "PravnickaOsoba",
  "valid_from": "2017-02-01T00:00:00+01:00",
  "valid_to": "2017-09-25T00:00:00+02:00",
  "detail_record_count": 1,
  "beneficial_owner_count": 2,
  "beneficial_owners": [
    {
      "name": "Jaroslav Vidra",
      "is_public_official": true,
      "valid_from": "2017-02-01T00:00:00+01:00",
      "valid_to": "2017-09-25T00:00:00+02:00"
    },
    {
      "name": "Katarína Vidrová",
      "is_public_official": true,
      "valid_from": "2017-02-01T00:00:00+01:00",
      "valid_to": "2017-09-25T00:00:00+02:00"
    }
  ],
  "source": "slovakia-public-sector-partners",
  "release_date": null,
  "source_url": "https://rpvs.gov.sk/opendatav2/Partneri?$expand=PartneriVerejnehoSektora,KonecniUzivateliaVyhod",
  "observed_at": "2026-09-18T06:17:38Z"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

The Partneri spine is paged by following @odata.nextLink exactly as the service supplies it ($top is disabled), expanded to partner detail + beneficial owners, bounded to maxRecords. Official $count is reconciled. A first-page failure charges nothing.

Source

https://rpvs.gov.sk/opendatav2/Partneri

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Registry record (registry_record)	$0.02	$0.02	$0.02	$0.01

Worked at the live Free-tier price:

• 8 registry records: $0.02 start + 8 × $0.02 = $0.18
• 25 registry records: $0.02 start + 25 × $0.02 = $0.52
• 2000 registry records: $0.02 start + 2000 × $0.02 = $40.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by rpvs.gov.sk. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (rpvs.gov.sk) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 2000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers rpvs.gov.sk. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• NY OCM Licence Registry — One structured registryrecord per record from the New York Office of Cannabis Management licence dataset (keyless NY Socrata jskf-tt3q, ~2,927 rows).…
• NYC DCWP Business Licence Registry — One structured registryrecord per record from the NYC Open Data DCWP licences resource (Socrata w7w3-xahh, ~69,885 rows). Public, logged-out, robots-…
• Poland KRS Company Registry — One structured registryrecord per record from the keyless api-krs.ms.gov.pl current-extract JSON (OdpisAktualny), logged-out. Public, logged-out, rob…
• Spain AEMPS Medicines Registry (CIMA) — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• Spain BORME Company Acts — One structured registryrecord per record from the boe.es open-data BORME daily summary (JSON) → per-province section XML chain, logged-out. Public, l…
• Spain CNMC Numbering Assignments — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.