Polish REGON Scraper - GUS Business Registry (no API key) avatar

Polish REGON Scraper - GUS Business Registry (no API key)

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Polish REGON Scraper - GUS Business Registry (no API key)

Polish REGON Scraper - GUS Business Registry (no API key)

Scrape Poland's REGON (GUS) registry anonymously: look up by NIP/REGON/KRS, discover companies by address + PKD, and get local units (jednostki lokalne) as separate rows. No API key required.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

getregdata

getregdata

Maintained by Community

Actor stats

0

Bookmarked

9

Total users

2

Monthly active users

8 days ago

Last modified

Share

Polish REGON Scraper - GUS Business Registry | Wyszukiwarka REGON (baza firm GUS)

Look up any Polish company in the official REGON business registry (GUS) by NIP, REGON, or KRS - structured JSON with identifiers, legal form, ownership, full address, registration dates, and PKD codes. Unlike the official BIR web service (which makes you register for a key tied to your identity), this needs no key, no registration, nothing to configure - and it returns local units (jednostki lokalne) as separate rows, so you see every branch, not just the headquarters.

What data do you get?

One record per entity or local unit:

{
"regon": "000010205",
"regon14": "00001020500190",
"nip": "5260006841",
"name": "BANK POLSKA KASA OPIEKI SPÓŁKA AKCYJNA - ODDZIAŁ W ŁODZI",
"recordType": "LOCAL_UNIT",
"parentRegon": "000010205",
"legalForm": "spółka akcyjna",
"ownershipForm": "Własność krajowych osób fizycznych",
"pkdMain": { "code": "64.19.Z", "name": "Pozostałe pośrednictwo pieniężne" },
"voivodeship": "ŁÓDZKIE",
"county": "Łódź",
"city": "Łódź",
"postalCode": "90-001",
"street": "ul. Piotrkowska",
"buildingNumber": "12",
"registrationDate": "1998-01-29",
"activityStartDate": "1929-10-17",
"website": "www.pekao.com.pl",
"scrapeStatus": "full",
"scrapedAt": "2026-05-26T08:00:00.000Z"
}
FieldDescription
regon / regon149-digit REGON / 14-digit REGON (local units)
nipPolish Tax ID
nameEntity or local-unit name
recordTypeHQ (legal entity) or LOCAL_UNIT (jednostka lokalna)
parentRegonParent company REGON for a local unit
legalForm / legalFormDetailBasic and detailed legal form
ownershipFormOwnership form (forma własności)
voivodeship / county / municipality / cityAddress names
postalCode / street / buildingNumber / unitNumberAddress detail
terytVoivodeship / terytCounty / terytMunicipalityTERYT codes
pkdMain / pkdMain PKD {code, name} and full PKD list
registrationDate / establishedDate / activityStartDate / endedDateDates
phone / email / websiteContact details where published
localUnitsCount / activitiesCountCounts from the report
scrapeStatus / scrapedAtPer-record status and timestamp

How much does the REGON data cost?

Pay per result - you are not charged for Apify platform usage, only a fixed price per record. The price drops on higher Apify subscription tiers.

VolumeCost
1 result$0.004
100 results~$0.40
1,000 results~$4.00
10,000 results~$40.00

There is effectively no start fee (only Apify's synthetic $0.00005 start event). Apify's $5 monthly free credit covers roughly 1,250 results. No subscription, no minimum.

Data comes from the official REGON register (Krajowy Rejestr Urzedowy Podmiotow Gospodarki Narodowej) at wyszukiwarkaregon.stat.gov.pl, maintained by GUS (Glowny Urzad Statystyczny / Statistics Poland). The registry is public - the actor reads only what GUS publishes openly. Extraction of this public data is permitted; you remain responsible for lawful, GDPR-compliant use of any personal data (e.g. sole-trader details) downstream.

How do I use it?

Click Try it and paste this input:

{ "searchMode": "nip", "identifiers": ["5260250995"] }

Look up by REGON or KRS by changing searchMode, and pass many identifiers in identifiers to enrich a whole list in one run.

Input options

ParameterTypeRequiredDefaultDescription
searchModestringNonipnip, regon, or krs
identifiersarrayYes-List of NIP / REGON / KRS numbers to look up
pkdSectionsarrayNo-Keep only records in these PKD 2007 sections (A-U)
pkdCodesarrayNo-Keep only records whose PKD starts with one of these
pkdMatchstringNoanyany = any reported PKD; main = only the main PKD
legalFormsarrayNo-Keep only entities whose legal form contains a phrase
fetchFullReportbooleanNotrueFetch each entity's full REGON report
fetchPkdbooleanNotrueFetch PKD activity codes
includeLocalUnitsbooleanNotrueInclude local units as separate rows
maxResultsintegerNo0Max records (0 = unlimited)

Search modes: nip (by tax ID), regon (by REGON, incl. local units), krs (by court-register number). Each takes the identifiers array.

Local units, not just headquarters

Most tools return only a company's registered seat. This actor returns every local unit (jednostka lokalna) as its own row - each physical branch or establishment with its own 14-digit REGON and address, linked to the parent through parentRegon. That is a real "one row per location" view of a company's footprint, which matters for site-level lead-gen, territory mapping, and physical-presence checks. Turn it off with includeLocalUnits: false if you only want headquarters.

What you can do with it

  • B2B lead generation - build targeted company lists by region and industry, filtering on PKD sections/codes.
  • KYB / company verification - confirm a company's identity, legal form, and status by NIP, REGON, or KRS.
  • CRM enrichment - append official identifiers, structured address (with TERYT codes), and PKD to your records.
  • Territory & market mapping - map business density and industry distribution across a region, down to branch level.
  • Bulk validation - clean and enrich thousands of NIP/REGON/KRS numbers in one run.

Run it from code

# cURL - start a run and get the dataset back
curl -X POST "https://api.apify.com/v2/acts/regdata~polish-regon-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "searchMode": "nip", "identifiers": ["5260250995"] }'
// Node.js - apify-client
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('regdata/polish-regon-scraper').call({ searchMode: 'nip', identifiers: ['5260250995'] });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
# Python - apify-client
from apify_client import ApifyClient
client = ApifyClient("YOUR_TOKEN")
run = client.actor("regdata/polish-regon-scraper").call(run_input={"searchMode": "nip", "identifiers": ["5260250995"]})
items = client.dataset(run["defaultDatasetId"]).list_items().items

Integrations

Runs anywhere Apify does: call it from the REST API, schedule recurring enrichment, 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 REGON? Yes. REGON is the official public business register published by GUS. Extraction of public data is permitted; you remain responsible for lawful, GDPR-compliant use of any personal data downstream.

Do I need a key or registration, like the official BIR service? No. The official BIR API makes you register for a user key tied to your identity. This actor needs no key and no registration - just an Apify account.

What export formats are supported? JSON, CSV, Excel, or XML, or read live via the API.

How do I get every branch, not just the HQ? Leave includeLocalUnits: true (the default). Each local unit comes back as its own row with a 14-digit REGON and parentRegon.

Can I filter by industry? Yes. Set pkdSections (A-U) or pkdCodes (prefix match). Keep fetchPkd: true so the filter has data to match on.

Can I search by name or address? No - lookup is by identifier (NIP / REGON / KRS). The official keyed REGON service does not support name or address search either.

Limitations

  • Lookup is by identifier (NIP / REGON / KRS); name and address search are not supported by the source register.
  • PKD and legal-form filters are applied per record, so keep fetchPkd: true for PKD filtering to take effect.
  • Employment figures are confidential in REGON and are not returned.

Part of a suite of official government registry actors - no public API to build or maintain, pay per result, nothing to configure.

CountryActors
PolandBDO · CRBR · KRS (financials) · EKW · KNF · KRS (board) · KRZ · MSiG · KYB check · PEP (Sejm) · REGON (sites) · REGON (this actor) · UOKiK
GermanyInsolvenzbekanntmachungen · Handelsregister
SpainBORME · Registro Mercantil · Registro Público Concursal
ItalyINI-PEC · Registro Imprese
AustriaEdiktsdatei · WKO
FranceSociete.com
BelgiumKBO / BCE
CzechiaISIR
SlovakiaRPVS
CyprusDRCOR
IrelandCRO
PortugalPublicações MJ
NigeriaCAC
ColombiaRUES
USACalifornia SoS · California UCC
UAEADGM
GlobalAdverse media

Common combinations: company register -> UBO -> insolvency/debtors -> adverse media is the standard KYB/onboarding chain.

For Poland that whole chain is one call: Poland KYB Risk Check takes a NIP or KRS and returns identity, beneficial owners and insolvency - screened against the company and every beneficial owner - as a single verdict, billed once per completed check.

Full suite: apify.com/regdata · Callable from any MCP client via mcp.apify.com

Informacje po polsku

Czym jest ten aktor?

Ten aktor to wyszukiwarka REGON - automatyczny dostep do oficjalnej bazy firm GUS. Sprawdz dowolny podmiot po NIP, REGON lub KRS. W przeciwienstwie do uslugi BIR, nie wymaga klucza ani rejestracji - nie musisz podawac swoich danych.

Co wyroznia ten aktor?

Zwraca jednostki lokalne jako osobne wiersze - kazdy oddzial firmy z wlasnym numerem REGON i adresem, powiazany z firma macierzysta przez parentRegon. To widok "jeden wiersz na lokalizacje", a nie tylko siedziba.

Dla kogo?

Do generowania leadow B2B, weryfikacji kontrahenta (KYB), wzbogacania danych w CRM oraz analizy rynku. Dane jako ustrukturyzowany JSON gotowy do CSV, Excela lub integracji przez API. Placisz wylacznie za wyniki - bez abonamentu.


Wyszukiwarka REGON - baza firm GUS przez API

Automatyczny dostep do rejestru REGON prowadzonego przez GUS: dane firm po NIP, REGON i KRS, kody PKD, jednostki lokalne jako osobne wiersze. Bez klucza API, bez rejestracji. Idealne do generowania leadow, weryfikacji kontrahentow (KYB) i wzbogacania danych. Rozliczenie wylacznie za uzycie.