Poland CRBR Beneficial Owners Scraper
Pricing
from $5.00 / 1,000 query results
Poland CRBR Beneficial Owners Scraper
Automate Polish beneficial owner verification for KYC/AML onboarding. Search the official public registry by NIP or KRS to return structured UBO data: names, citizenship, control nature, ownership %. Pay-per-result, no subscription. Pairs with debtor and KNF checks.
Pricing
from $5.00 / 1,000 query results
Rating
0.0
(0)
Developer
getregdata
Maintained by CommunityActor stats
0
Bookmarked
14
Total users
7
Monthly active users
2 days ago
Last modified
Categories
Share
Poland CRBR Beneficial Owners Scraper | Rejestr Beneficjentow Rzeczywistych
Verify the beneficial owners (UBO) of any Polish company in bulk, straight from Poland's official Central Register of Beneficial Owners (CRBR) - structured JSON, beyond what the register's single manual web lookup allows. Search by NIP, KRS, company name, or a beneficiary's PESEL and get back the owners, the nature of control resolved into the wording of the AML Act (not a bare code), the officers who filed the declaration, and any discrepancy reports.
No login, no API key, nothing to configure - paste a NIP and get a compliance-ready record back in seconds. It reads the register's data directly (no browser), so runs finish fast, and the live run and success figures are shown by Apify above this README - you never have to take our word for it.
What data do you get?
One structured record per company. A real result (PESEL masked here for documentation only; the actor returns the full value):
{"requestId": "0C7F5D8BF6924B109B3D0DBFACE902D7","name": "COMARCH SPÓŁKA AKCYJNA","nip": "6770065406","krs": "0000057567","legalForm": "Spółka akcyjna","postalCode": "31-864","voivodeship": "MAŁOPOLSKIE","city": "KRAKÓW","street": "ALEJA JANA PAWŁA II","houseNumber": "39A","periodStart": "2026-07-09","periodEnd": "2026-07-09","corrected": false,"hasDiscrepancies": false,"discrepancyCount": 0,"proceeding": null,"found": true,"beneficialOwners": [{"firstName": "JAROSŁAW","lastName": "MIKOS","pesel": "670120*****","citizenship": "POLSKA","countryOfResidence": "POLSKA","entitlements": [{"natureOfControl": "osoba fizyczna zajmująca wyższe stanowisko kierownicze, o której mowa w art. 2 ust. 2 pkt.1 lit. a tiret 5 ustawy AML","natureOfControlCode": "002","controlBasisCode": 3}]}],"representatives": [{ "firstName": "ZBIGNIEW", "lastName": "RYMARCZYK", "role": "zgłaszający - członek zarządu" },{ "firstName": "IWONA", "lastName": "KASPRZYK", "role": "zgłaszający - prokurent" }],"sourceUrl": "https://crbr.podatki.gov.pl/"}
By default the actor returns the current entry (one row per company). Pass dateFrom (e.g. "2019-10-13", the register's start) to retrieve historical filings.
How much does CRBR data cost?
Pay per result - you are not charged for Apify platform usage, only a small start fee plus a fixed price per company record. The per-record price drops on higher Apify subscription tiers.
| Event | Cost |
|---|---|
| Actor start (per run) | $0.025 |
| Each company record | $0.008 |
| Volume | Total |
|---|---|
| 1 company, single run | $0.033 |
| 100 companies, one batch run | $0.825 |
| 1,000 companies, one batch run | $8.03 |
| 10,000 companies, one batch run | $80.03 |
Batch your queries and the start fee amortises to almost nothing. Apify's $5 monthly free credit covers roughly 620 company records in one batch run, or about 150 individual lookups. No subscription, no seats, no minimum - and failed lookups are never charged (see the FAQ).
Is it legal, and where does the data come from?
All data comes from the official CRBR register at crbr.podatki.gov.pl, maintained by Poland's Ministry of Finance under the Anti-Money Laundering Act (ustawa z dnia 1 marca 2018 r. o przeciwdzialaniu praniu pieniedzy oraz finansowaniu terroryzmu). The register is public - it exists precisely so obliged institutions can verify beneficial ownership. Companies face fines of up to 1,000,000 PLN for failing to file or for filing false UBO declarations.
Extraction of this public data is permitted. Every record carries the requestId and the presentation period, so any answer can be traced back to the exact filing it came from - your audit trail. You remain responsible for lawful, GDPR-compliant use of the personal data (owner names, PESEL) downstream.
How do I use it?
Click Try it and paste this input:
{ "nip": "6770065406" }
Or look up by KRS ({ "krs": "0000057567" }), by company name, or by a person's PESEL to find companies where they are a beneficial owner. To screen many companies in one run, pass a queries array - the start fee then amortises across all of them.
Input options
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
nip | string | No | - | Polish Tax ID for a single query |
krs | string | No | - | KRS number for a single query |
companyName | string | No | - | Company name for a single query (partial match) |
queries | array | No | - | Batch queries - array of {nip, krs, name, pesel} objects, or bare strings |
dateFrom | string | No | today | Start date (YYYY-MM-DD); pass 2019-10-13 for full history |
dateTo | string | No | today | End date (YYYY-MM-DD) |
At least one of nip, krs, companyName, or queries must be provided.
Resolved, not raw - the difference that matters
CRBR does not tell you why someone is a beneficial owner. It stores a number. charakterUdzialu: 3 is all the register gives you, and a record that says "charakter 3" cannot go into a client file.
This actor returns the number and what it means:
| Value | |
|---|---|
controlBasisCode | 3 |
natureOfControlCode | "002" |
natureOfControl | "osoba fizyczna zajmująca wyższe stanowisko kierownicze, o której mowa w art. 2 ust. 2 pkt.1 lit. a tiret 5 ustawy AML" |
Read it, or join on it. You never maintain a code table. Comarch is the instructive case: it declares no owner above 25%, so its UBOs are senior managing officials with no ownership percentage at all - a tool that only reports percentages returns nothing useful here. Companies with a direct stake instead carry a natureOfControl such as "wspólnik spółki jawnej" together with an amount and unit.
Fields that are easy to miss
These come from parts of the CRBR response that are simple to skip, and they are usually the ones a reviewer asks about:
| Field | Why it matters |
|---|---|
representatives[] | The officers who signed the declaration (członek zarządu, prokurent) - your evidence trail. |
hasDiscrepancies, discrepancyCount | Discrepancy reports filed against the entry. Obliged institutions have a statutory duty to report UBO discrepancies. |
requestId + periodStart/periodEnd | CRBR's own query identifier and reporting period - reproducible proof of what the register said, and when. |
trustRights, groupName | Trust entitlements and group-beneficiary name, for trust and group structures. |
proceeding | Insolvency or liquidation proceedings noted against the company. |
foreignAddress, foreignTrustRegister | Foreign seat and foreign trust register, where they apply. |
corrected | Whether the entry is a correction of an earlier filing. |
What you can do with it
- KYC / AML compliance - verify UBO declarations as part of customer due diligence (CDD) and enhanced due diligence (EDD), and capture the
requestIdfor your file. - Bank & fintech onboarding - screen a counterparty's beneficial owners before account opening; pass a
queriesbatch to clear a whole onboarding queue in one run. - M&A due diligence - identify the ultimate controllers of an acquisition target, including senior-managing-official UBOs that percentage-only tools miss.
- Ongoing monitoring - schedule a recurring run over your portfolio and catch new filings, corrections, or discrepancy reports.
- Investigative research - trace ownership networks by searching on a person's PESEL to find every company they beneficially own.
Flat export for spreadsheets
The dataset nests owners inside their company, so one company is one billable record. To get one row per owner, reshape on export - this does not create extra billable results:
https://api.apify.com/v2/datasets/<datasetId>/items?format=csv&unwind=beneficialOwners
Run it from code
# cURL - start a run and get the dataset backcurl -X POST "https://api.apify.com/v2/acts/regdata~crbr-beneficial-owners-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \-H "Content-Type: application/json" \-d '{ "nip": "6770065406" }'
// Node.js - apify-clientimport { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: 'YOUR_TOKEN' });const run = await client.actor('regdata/crbr-beneficial-owners-scraper').call({ nip: '6770065406' });const { items } = await client.dataset(run.defaultDatasetId).listItems();
# Python - apify-clientfrom apify_client import ApifyClientclient = ApifyClient("YOUR_TOKEN")run = client.actor("regdata/crbr-beneficial-owners-scraper").call(run_input={"nip": "6770065406"})items = client.dataset(run["defaultDatasetId"]).list_items().items
Integrations
Runs anywhere Apify does: call it from the REST API, schedule recurring UBO checks, pipe results into n8n / Make / Zapier, or use it from any MCP client (Claude, Cursor) via mcp.apify.com.
FAQ
Is it legal to scrape CRBR? Yes. CRBR is an official, public register published by the Polish Ministry of Finance for exactly this kind of beneficial-ownership verification. Extraction of public data is permitted; you remain responsible for lawful, GDPR-compliant use of the personal data (names, PESEL) downstream.
Do I need a CRBR account or API key? No. No login, no key, nothing to configure - the register is public and the actor handles retrieval. You only need an Apify account to run it.
Am I charged if a lookup fails? No. A transport failure is never written to the dataset or billed - failures are reported in the run's ERRORS key-value record and the run status message. A definitive "no entries in CRBR" is returned and charged, because that is a real answer (the company has no filing), not a failure.
What export formats are supported? JSON, CSV, Excel, or XML, or read live via the API. For one row per beneficial owner in a spreadsheet, add unwind=beneficialOwners on export (see above).
Why does a company show UBOs with no ownership percentage? Because CRBR records the basis of control, not always a percentage. When no one owns above 25%, the beneficial owners are senior managing officials (natureOfControl = "osoba zajmująca wyższe stanowisko kierownicze") and carry no amount. That is the correct legal answer, and the resolved natureOfControl wording tells you exactly why.
Which companies are covered? All legal entities registered in KRS. Sole proprietorships (CEIDG) are not in CRBR and will return found: false.
How current is the data? It is read live from the register at query time. Note that declarations are self-reported - the Ministry does not independently verify them, and companies must update within 7 business days of an ownership change (delays occur in practice). This is exactly why the hasDiscrepancies field matters.
Limitations
- CRBR covers KRS-registered legal entities only - sole proprietorships (CEIDG) are not included and return
found: false. - Data reflects self-reported UBO declarations; the Ministry of Finance does not independently verify them (which is why
hasDiscrepanciesexists). - Companies must update declarations within 7 business days of an ownership change, but delays occur in practice.
Related actors
Part of a suite of official government registry actors - no public API, pay per result, no keys to supply.
| Country | Actors |
|---|---|
| Poland | REGON/GUS · KRS financials · KRS board · CRBR UBO (this actor) · KRZ debtors · MSiG gazette · KNF · PEP · EKW land · UOKiK · BDO waste · Premises |
| Germany | Handelsregister · Insolvency |
| Spain | Company directory · BORME acts · Concursal |
| Italy | Registro Imprese · PEC lookup |
| Austria | WKO directory · Ediktsdatei |
| France | Societe.com |
| Belgium | KBO/BCE |
| Czechia | ISIR insolvency |
| Slovakia | RPVS UBO |
| UAE | ADGM register |
| USA | California SoS · California UCC liens |
| Global | Adverse media |
Common combination: company register -> UBO (this actor) -> insolvency/debtors -> adverse media is the standard KYB/onboarding chain.
Full suite: apify.com/regdata · Callable from any MCP client via mcp.apify.com
Informacje po polsku
Czym jest ten aktor?
Ten aktor umozliwia automatyczne odpytywanie Centralnego Rejestru Beneficjentow Rzeczywistych (CRBR) - rejestru prowadzonego przez Ministerstwo Finansow, w ktorym kazda polska osoba prawna musi ujawniac swoich beneficjentow rzeczywistych. Aktor odpytuje rejestr bezposrednio, wiec uruchomienia koncza sie w kilka sekund.
Dla kogo?
Dla oficerow compliance AML w bankach i instytucjach finansowych weryfikujacych deklaracje UBO, kancelarii prawnych identyfikujacych rzeczywistych kontrolerow w transakcjach M&A, firm fintechowych automatyzujacych screening KYC przy onboardingu, doradcow podatkowych weryfikujacych struktury wlascicielskie oraz dziennikarzy sledczych sledzacych sieci wlascicielskie spolek.
Co mozna sprawdzic?
Wyszukiwanie po NIP, KRS, nazwie firmy (dopasowanie czesciowe) lub PESEL beneficjenta, z obsluga przetwarzania wsadowego. Kazdy wynik zawiera nazwe firmy, NIP, KRS, forme prawna, adres, liste beneficjentow rzeczywistych oraz - co najwazniejsze - charakter uprawnien opisany slowami ustawy AML, a nie sam kod liczbowy. Zwracamy takze osoby zglaszajace deklaracje (czlonek zarzadu, prokurent) i informacje o rozbieznosciach. Placisz tylko za to, co pobierzesz; nieudane zapytania nie sa naliczane.
Changelog
1.2 - fuller records, flat export
- Nature of control now ships both the resolved wording from the AML Act and the raw registry codes (
natureOfControlCode,controlBasisCode,ownershipTypeCode,unitCode), so you can read it or join on it. - New fields:
trustRightsandgroupNameon each owner;proceeding,foreignAddress,foreignTrustRegister, anddiscrepancyCounton the company. - Flat, one row per owner for spreadsheets - add
unwind=beneficialOwnerson export. It reshapes the same records; it does not create extra billable results. - Corrected the documented output fields: the real control fields are under
beneficialOwners[].entitlements[].
1.1 - failures no longer charged
- Failed lookups are no longer written to the dataset, so a transport error is never charged. Failures are reported in the run's
ERRORSkey-value record and the status message. A definitive "no entries in CRBR" result is still returned (and charged) - that is an answer, not a failure. - Batch queries run several at a time with automatic retry; results stay in the same order as your input.
Weryfikacja beneficjentow rzeczywistych - CRBR online
Automatyczna weryfikacja beneficjentow rzeczywistych z Centralnego Rejestru Beneficjentow Rzeczywistych (CRBR). Wyszukiwanie po NIP, KRS, nazwie firmy lub PESEL. Niezbedne narzedzie do weryfikacji KYC/AML, due diligence i onboardingu klientow. Bez miesiecznego abonamentu - placisz tylko za zapytania.