🔔 Poland VAT Whitelist Verifier

One vat_check verdict per queried identifier against Poland's official Ministry of Finance VAT whitelist (Wykaz podatników VAT) — keyless, logged-out API.

Difference: A verification CHECK, not a data dump: submit NIP, REGON, or bank-account identifiers and get one definitive verdict each — ACTIVE / EXEMPT / NOT_ACTIVE / NOT_LISTED — with the subject's name, status, REGON/KRS, and the official request identifier and query date carried as evidence on every verdict.

Output is one vat_check row per result; billing is pay-per-event, the value event being one poland vat whitelist verifier (a $0.02 start fee per run, then $0.05 per poland vat whitelist verifier). Source: wl-api.mf.gov.pl.

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 801HeFDZMkAyhqHlv on build 0.1.7 (2026-09-23), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

query_value	query_date	nip	subject_name	regon	krs
7740001454	2026-08-07	7740001454	ORLEN SPÓŁKA AKCYJNA	610188201	0000028860

The run finished with the status message: 1 query(ies): 1 definitive verdict(s) charged, 0 unbilled (malformed/service-fault) | vat_check charged=1

✅ 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):

• query_type (string/null) — e.g. nip
• query_value (string/null) — e.g. 7740001454
• query_date (string/null) — e.g. 2026-08-07
• nip (string/null) — e.g. 7740001454
• subject_name (string/null) — e.g. ORLEN SPÓŁKA AKCYJNA
• status_vat (string/null) — e.g. Czynny
• regon (string/null) — e.g. 610188201
• krs (string/null) — e.g. 0000028860
• residence_address (string/null) — null in every sample row
• working_address (string/null) — e.g. CHEMIKÓW 7, 09-411 PŁOCK
• registration_legal_date (string/null) — e.g. 1993-07-05
• registration_denial_date (string/null) — null in every sample row
• restoration_date (string/null) — null in every sample row
• removal_date (string/null) — null in every sample row
• verdict (string/null) — e.g. ACTIVE
• request_id (string/null) — e.g. vmroC-98jig6n
• faults (string/null) — null in every sample row
• record_type (string) — e.g. vat_check
• source (string/null) — e.g. Poland Ministry of Finance VAT whitelist (Wykaz podatników VAT) official API
• outcome (string/null) — e.g. answer
• input (string/null) — e.g. 7740001454
• outcome_reason (string/null) — null in every sample row
• observed_at (string/null) — null in every sample row

What you get

One verdict per identifier. Any definitive official answer (active VAT payer found, OR definitively absent from the whitelist) is delivered with the official requestId + query date. Malformed input and service faults are delivered as unbilled status rows.

⚙️ Sample inputs

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

{
  "queries": [
    "7740001454"
  ],
  "queryType": "nip",
  "date": "2026-08-07"
}

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

2. A smaller, narrowed run

{
  "queries": [
    "7740001454"
  ],
  "queryType": "nip",
  "date": "2026-08-07"
}

A bounded run for checking the field shape before scheduling. queryType narrows what the source is asked for.

3. A full-size run

{
  "queries": [
    "7740001454"
  ],
  "queryType": "nip",
  "date": "2026-08-07"
}

The same input run on a schedule; each run is billed only for what it delivers.

🧾 JSON sample record

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

{
  "query_type": "nip",
  "query_value": "7740001454",
  "query_date": "2026-08-07",
  "nip": "7740001454",
  "subject_name": "ORLEN SPÓŁKA AKCYJNA",
  "status_vat": "Czynny",
  "regon": "610188201",
  "krs": "0000028860",
  "residence_address": null,
  "working_address": "CHEMIKÓW 7, 09-411 PŁOCK",
  "registration_legal_date": "1993-07-05",
  "registration_denial_date": null,
  "restoration_date": null,
  "removal_date": null,
  "verdict": "ACTIVE",
  "request_id": "vmroC-98jig6n",
  "faults": null,
  "record_type": "vat_check",
  "source": "Poland Ministry of Finance VAT whitelist (Wykaz podatników VAT) official API",
  "outcome": "answer",
  "input": "7740001454",
  "outcome_reason": null
}

🔧 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 poland vat whitelist verifier is charged at the moment it is pushed (vat_check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Each identifier is validated locally (format + NIP checksum) before any network call — a malformed identifier is rejected and never billed. Valid identifiers are queried against the official API for the given date; a definitive answer bills once. A non-200 or network fault from the official API is an unbilled SERVICE_FAULT, never a wrong verdict. robots is honoured per origin.

Source

https://wl-api.mf.gov.pl/api/search/{nip|regon|bank-account}/{value}?date=YYYY-MM-DD

Attribution

Source: Ministerstwo Finansów Rzeczypospolitej Polskiej — Wykaz podatników VAT (official VAT whitelist API).

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
Poland VAT Whitelist Verifier (vat_check)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price:

• 1 poland vat whitelist verifiers: $0.02 start + 1 × $0.05 = $0.07
• 25 poland vat whitelist verifiers: $0.02 start + 25 × $0.05 = $1.27
• 100 poland vat whitelist verifiers: $0.02 start + 100 × $0.05 = $5.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: 1 query(ies): 1 definitive verdict(s) charged, 0 unbilled (malformed/service-fault) | vat_check charged=1.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by wl-api.mf.gov.pl. 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 (wl-api.mf.gov.pl) 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 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 wl-api.mf.gov.pl. 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.
• Fewer rows than expected → the source had fewer items in scope → widen the input.
• 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

• PDF Operations Toolkit — Runs split / merge / reorder / compress / rasterize on supplied PDFs and returns a per-operation manifest reconciling every input page to an output p…
• Philadelphia L&I Business Licenses — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured
• 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…
• ESMA Prospectus Register Check — same family, different source
• Seattle Business License Tax Certificates — Seattle Business License Tax Certificates
• Slovakia Public-Sector Partners Register — Slovakia Public-Sector Partners Register
• 🏢 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.