🔎 EU EORI Customs Registration Check

A per-identity validity check: submit EORI numbers, get one official validity answer each. Billed per definitive validity answer — valid or not-valid — while malformed input and service faults are returned but never charged.

Output is one eori_answer row per result; billing is pay-per-event, the value event being one eori registration check (a $0.02 start fee per run, then $0.05 per eori registration check). Source: ec.europa.eu, eori.ws.eos.dds.s, schemas.xmlsoap.org.

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

Who buys this

Buyers usually search for EORI check or EORI number validation.

• Sales and lead-generation teams building lists from EORI check.
• KYB, onboarding and compliance teams checking EORI number validation.
• Market researchers and data teams that need the official record as rows.

📊 Sample Output

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

eori	registered	status_code	status_descr	request_date	input
IT00159560366	True	0	Valid	28/09/2026	IT00159560366
BE0417497106	True	0	Valid	28/09/2026	BE0417497106
DE123456789012345	False	1	Not valid	28/09/2026	DE123456789012345

The run finished with the status message: NORMAL: 3 billable answer(s), 0 definitive non-billable (not-found/ambiguous), 0 unavailable, 0 unparseable of 3 | eori-registration-check billable=3 | eori-registration-check charged=3

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

• eori (string/null) — e.g. IT00159560366
• registered (boolean/null) — e.g. True
• status_code (string/null) — e.g. 0
• status_descr (string/null) — e.g. Valid
• name (string/null) — e.g. FERRARI S.P.A.
• street (string/null) — e.g. VIA EMILIA EST 1163
• postal_code (string/null) — e.g. 41122
• city (string/null) — e.g. MODENA
• country (string/null) — e.g. Italy
• consent_given (boolean/null) — e.g. True
• request_date (string/null) — e.g. 28/09/2026
• record_type (string/null) — e.g. eori_answer
• input (string/null) — e.g. IT00159560366
• source (string/null) — e.g. https://ec.europa.eu/taxation_customs/dds2/eos/validation/services/validation
• outcome (string/null) — e.g. answer
• outcome_reason (string/null) — e.g. valid; trader identity withheld — consent not given

✅ What you get

• eori (string/null) — e.g. IT00159560366
• registered (boolean/null) — e.g. True
• status_code (string/null) — e.g. 0
• status_descr (string/null) — e.g. Valid
• name (string/null) — e.g. FERRARI S.P.A.
• street (string/null) — e.g. VIA EMILIA EST 1163
• postal_code (string/null) — e.g. 41122
• city (string/null) — e.g. MODENA
• country (string/null) — e.g. Italy
• consent_given (boolean/null) — e.g. True
• request_date (string/null) — e.g. 18/09/2026
• record_type (string/null) — e.g. eori_answer
• input (string/null) — e.g. IT00159560366
• source (string/null) — e.g. https://ec.europa.eu/taxation_customs/dds2/eos/validation/services/validation
• outcome (string/null) — e.g. answer
• outcome_reason (string/null) — e.g. valid; trader identity withheld — consent not given

✅ What you get

• eori (string/null) — e.g. IT00159560366
• registered (boolean/null) — e.g. True
• status_code (string/null) — e.g. 0
• status_descr (string/null) — e.g. Valid
• name (string/null) — e.g. FERRARI S.P.A.
• street (string/null) — e.g. VIA EMILIA EST 1163
• postal_code (string/null) — e.g. 41122
• city (string/null) — e.g. MODENA
• country (string/null) — e.g. Italy
• consent_given (boolean/null) — e.g. True
• request_date (string/null) — e.g. 17/09/2026
• record_type (string/null) — e.g. eori_answer
• input (string/null) — e.g. IT00159560366
• source (string/null) — e.g. https://ec.europa.eu/taxation_customs/dds2/eos/validation/services/validation
• outcome (string/null) — e.g. answer
• outcome_reason (string/null) — e.g. valid; trader identity withheld — consent not given

What you get

One record per submitted number. Each definitive answer carries registered (true/false), the status description, and the official request date; a valid registration also carries the trader's name/address verbatim (honest null with a reason when consent is withheld). Malformed input and service-unavailable outcomes are distinguished in the outcome field and are not billed. A run with no definitive answer at all fails loud and charges nothing.

⚙️ Sample inputs

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

{
  "eoriNumbers": [
    "IT00159560366",
    "BE0417497106",
    "DE123456789012345"
  ]
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 3 × $0.05 eori-registration-check = $0.17 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 PGFOcZw4g3Nn1pqjU, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "eori": "IT00159560366",
  "registered": true,
  "status_code": "0",
  "status_descr": "Valid",
  "name": "FERRARI S.P.A.",
  "street": "VIA EMILIA EST 1163",
  "postal_code": "41122",
  "city": "MODENA",
  "country": "Italy",
  "consent_given": true,
  "request_date": "28/09/2026",
  "record_type": "eori_answer",
  "input": "IT00159560366",
  "source": "https://ec.europa.eu/taxation_customs/dds2/eos/validation/services/validation",
  "outcome": "answer",
  "outcome_reason": null
}

🔧 How it works

Source. The actor reads ec.europa.eu, eori.ws.eos.dds.s, schemas.xmlsoap.org — endpoints: http://eori.ws.eos.dds.s/, http://schemas.xmlsoap.org/soap/envelope/, https://ec.europa.eu/taxation_customs/dds2/eos/validation/services/validation. 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 eori registration check is charged at the moment it is pushed (eori-registration-check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

🔧 How it works

How it behaves

Each EORI number is validated against the European Commission's official EORI validation service. Any definitive validity answer bills — a valid registration (with the official request date; if the trader has not consented to publish their identity, name/address are honest null with a reason) and a not-valid result (also carrying the official request date) are both completed official answers and are both billed. A malformed EORI number is unparseable and not billed; a service outage (SOAP fault / HTTP error) is unavailable and not billed.

Billing

Event	FREE	BRONZE	SILVER	GOLD+
apify-actor-start (one-time actor start)	$0.02	$0.02	$0.02	$0.02
eori-registration-check (per completed official answer)	$0.05	$0.045	$0.04	$0.0335

Charged once per definitive validity answer (valid or not-valid). Malformed input and service-fault outcomes are emitted but never charged. Start fee $0.02.

Source

https://ec.europa.eu/taxation_customs/dds2/eos/validation/services/validation

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
Eori Registration Check (eori-registration-check)	$0.05	$0.045	$0.04	$0.0335

Worked at the live Free-tier price:

• 3 eori registration checks: $0.02 start + 3 × $0.05 = $0.17
• 25 eori registration checks: $0.02 start + 25 × $0.05 = $1.27
• 100 eori registration 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 1024 MB.

Yield on the sample run: NORMAL: 3 billable answer(s), 0 definitive non-billable (not-found/ambiguous), 0 unavailable, 0 unparseable of 3 | eori-registration-check billable=3 | eori-registration-check charged=3.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by ec.europa.eu, eori.ws.eos.dds.s, schemas.xmlsoap.org. 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 (ec.europa.eu, eori.ws.eos.dds.s, schemas.xmlsoap.org) 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 company registry checks actors?
A: Same output shape and billing model; this one covers ec.europa.eu, eori.ws.eos.dds.s, schemas.xmlsoap.org. 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

• Connecticut Certified Suppliers — One record per CT certified small business (certification type, services, codes, DAS prequalification, employee-size band, dates, location) from the…
• CQC Care Provider Directory Scraper — One care_provider_record per CQC-registered location: name, address, postcode, phone, website, service types, latest-check date, specialisms, provide…
• CQC Provider Verification Check — Verify UK care providers and locations against the official CQC weekly directory — one present/absent verdict per identifier. Billed per PRESENT verd…
• EU VAT Validator — VIES per-answer check — Validate EU VAT numbers against the official EU VIES service — one verdict per number with the registered name and date. No API key; pay per complete…
• Finland PRH Business Filing Lookup — A per-identity check: submit identifiers, get one official answer each. Billed per completed official resolution — a not-found, ambiguous, or unavail…
• Finland PRH YTJ Company Registry — One record per Finnish company from the official PRH open-data YTJ API v3 (business ID, current name, legal form, main business line, primary address…
• 🏢 About NexGen Watch — NexGen Watch is a catalog 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.