🔔 Netherlands ANBI Status Check

One anbi_status_check verdict per queried body — resolve an RSIN or organisation name against the current official Belastingdienst ANBI file, keyless and logged-out.

Difference: A verification CHECK, not a dump. Submit RSIN fiscal numbers or exact names and get one definitive verdict each — FOUND (in the current ANBI file) with dossier, RSIN, name, place, start date, status and any revocation date as evidence; or NOT_FOUND / AMBIGUOUS / SERVICE_FAULT. Rides the same official file as the nl-anbi-register roster.

Output is one anbi_status_check row per result; billing is pay-per-event, the value event being one anbi status check (a $0.02 start fee per run, then $0.05 per anbi status check). Source: download.belastingdienst.nl.

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

input	query	query_kind	verdict	name	anbi_status
001000652	001000652	fiscal	FOUND	LECTORIUM ROSICRUCIANUM	listed_in_current_file
LECTORIUM ROSICRUCIANUM	LECTORIUM ROSICRUCIANUM	name	FOUND	LECTORIUM ROSICRUCIANUM	listed_in_current_file
ZZZ Notareal ANBI 999	ZZZ Notareal ANBI 999	name	NOT_FOUND

The run finished with the status message: PARTIAL: 2 resolved (1 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 3 | answers billable=2 | anbi_status_check charged=2

✅ 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. anbi_status_check
• input (string/null) — e.g. 001000652
• query (string/null) — e.g. 001000652
• query_kind (string/null) — e.g. fiscal
• source (string/null) — e.g. https://download.belastingdienst.nl/data/anbi/anbi.zip
• verdict (string/null) — e.g. FOUND
• dossier_number (string/null) — e.g. 6
• fiscal_number_rsin (string/null) — e.g. 001000652
• name (string/null) — e.g. LECTORIUM ROSICRUCIANUM
• place (string/null) — e.g. HAARLEM
• anbi_start_date (string/null) — e.g. 2008-01-01
• revocation_date (string/null) — null in every sample row
• anbi_status (string/null) — e.g. listed_in_current_file
• candidates (string/null) — null in every sample row
• unbilled_reason (string/null) — e.g. not_found: not in the current public ANBI file

✅ What you get

What you get

One verdict per query. Only a completed official answer — a FOUND resolution — is billed. NOT_FOUND, AMBIGUOUS and service-fault are distinguished, emitted, and never billed; a run that resolves nothing fails loud and charges nothing. Presence in the current file is the status; revocation date is carried verbatim, never invented.

⚙️ Sample inputs

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

{
  "queries": [
    "001000652",
    "LECTORIUM ROSICRUCIANUM",
    "ZZZ Notareal ANBI 999"
  ]
}

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

This actor takes no size cap or filter beyond the input above, so the Store example is the one input to run; put it on a schedule to keep the data current.

🧾 JSON sample record

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

{
  "record_type": "anbi_status_check",
  "input": "001000652",
  "query": "001000652",
  "query_kind": "fiscal",
  "source": "https://download.belastingdienst.nl/data/anbi/anbi.zip",
  "verdict": "FOUND",
  "dossier_number": "6",
  "fiscal_number_rsin": "001000652",
  "name": "LECTORIUM ROSICRUCIANUM",
  "place": "HAARLEM",
  "anbi_start_date": "2008-01-01",
  "revocation_date": null,
  "anbi_status": "listed_in_current_file",
  "candidates": null,
  "unbilled_reason": null
}

🔧 How it works

Source. The actor reads download.belastingdienst.nl — endpoints: https://download.belastingdienst.nl/data/anbi/anbi.zip. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each anbi status check is charged at the moment it is pushed (anbi_status_check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

How it behaves

The official anbi.zip is fetched once behind a CRC gate and indexed by RSIN and name; each query resolves against the index. Bounded per run.

Source

https://download.belastingdienst.nl/data/anbi/anbi.zip

Attribution

Source: Belastingdienst (Netherlands Tax Administration) — ANBI open data (CC0).

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
ANBI status check (anbi_status_check)	$0.05	$0.045	$0.04	$0.0335

Worked at the live Free-tier price:

• 3 anbi status checks: $0.02 start + 3 × $0.05 = $0.17
• 25 anbi status checks: $0.02 start + 25 × $0.05 = $1.27
• 100 anbi status checks: $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: PARTIAL: 2 resolved (1 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 3 | answers billable=2 | anbi_status_check charged=2.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by download.belastingdienst.nl. It collects only what the source publishes to any visitor, 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 (download.belastingdienst.nl) 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 download.belastingdienst.nl. 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; 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

• Missouri Active Alcohol Licenses — One record per associated-person row on each active Missouri alcohol licence (licence number + type, licensee, DBA name, premise address, county, and…
• ESMA Money Market Funds Register Check — One mmf_check verdict per queried fund — resolve a money market fund against the official ESMA MMF register, keyless and logged-out
• Netherlands ANBI Register — One structured anbi_record per ANBI decision from the Netherlands Tax Administration's official weekly open-data file — keyless, logged-out, CC0
• NOAA GHCN-Daily Observations — Structured daily climate observations from the U.S. NOAA/NCEI Global Historical Climatology Network - Daily (GHCN-Daily), read directly from the offi…
• NOAA GHCN-Monthly Average Temperature — Structured monthly average-temperature (TAVG) station-year records from the U.S
• NOAA ISD Hourly Surface Observations — Structured hourly surface weather observations from the U.S. NOAA/NCEI Integrated Surface Database (ISD), read directly from the official public bulk…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of more than 300 public data 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.