One API for VAT validation across 32 countries

Avatcado checks VAT and GST numbers live against VIES, HMRC, BFS, Bronnoysund and ABR and stores each result, with the consultation number when one is returned. When VIES cannot answer, eligible checks fall back to national registers (Pro and Business) or stored results (any plan).

500 free validations/month. No credit card.

What the API includes

All six work with one API key. Batch and async validation need Pro or Business.

32 countries

EU-27 via VIES, UK via HMRC, Switzerland and Liechtenstein via BFS, Norway via Bronnoysund, Australia via ABR. Each lookup hits the official government source.

Built-in audit trail

Every validation is stored with a timestamp, the raw upstream response, and a consultation number where the source provides one (VIES, HMRC). Exportable for tax audits.

Caching

Repeat lookups return in milliseconds from cache. When an upstream source goes down, Avatcado can serve the most recent stored result for that number, flagged with meta.cached and meta.stale. Requester checks skip the cache unless you pass cache=true.

Typed SDKs

@avatcado/node for TypeScript and avatcado on PyPI. Full type definitions, structured errors, and autocomplete out of the box. OpenAPI spec included.

Test mode

Magic VAT numbers for key countries (DE, GB, FR, CH, NO), plus deterministic test behavior everywhere else. No upstream calls, no quota usage. Safe to run in CI.

Batch and async

Validate up to 50 numbers per synchronous batch request, or up to 1,000 asynchronously on Business with webhook delivery when results are ready. Deduplicated counting.

Also checks EORI numbers. The same API key checks customs numbers for the 27 EU member states, XI and GB against the European Commission and HMRC registers. One request per check, on every plan.

EORI validation API

Audit trail, built in

Avatcado stores every validation with the upstream response for as long as your account is active. Export the history as JSON to keep each result with your own records.

{
  "data": {
    "valid": true,
    "vat_number": "NL123456789B01",
    "country_code": "NL",
    "company": {
      "name": "Example B.V.",
      "address": "Keizersgracht 123, 1015 Amsterdam"
    },
    "consultation_number": "WAAV4B5xQ3UzR7kP",
    "requested_at": "2026-04-07T10:30:00Z"
  },
  "meta": {
    "request_id": "req_abc123",
    "source_status": "live"
  }
}

What the stored record gives you

  • Stored automatically with every validation
  • Consultation numbers from VIES and HMRC (with a requester VAT number from the same system: EU for an EU number, UK for a UK number)
  • Exportable as JSON via the data export endpoint

A reverse-charge or zero-rated invoice needs evidence of the customer's VAT status. The stored record holds the registry result, its timestamp and, when VIES or HMRC returned one, the consultation number. Keep it with the invoice; the tax treatment itself is still your decision.

Country coverage

One endpoint, one response shape. Avatcado routes to the correct government source automatically.

EUEU (27 member states + XI)
SourceVIES
Returns namereturned for most countries, see footnote
Returns addressreturned for most countries, see footnote
Consultation #with requester VAT number, see footnote
GBUnited Kingdom
SourceHMRC
Returns namereturned
Returns addressreturned
Consultation #with requester VAT number, see footnote
Fallback when VIES is downCached result
CHSwitzerland
SourceBFS UID Register
Returns namereturned
Returns addressreturned
Consultation #not returned
Fallback when VIES is downCached result
LILiechtenstein
SourceBFS UID Register
Returns namereturned
Returns addressreturned
Consultation #not returned
Fallback when VIES is downCached result
NONorway
SourceBronnoysund Register Centre
Returns namereturned
Returns addressreturned
Consultation #not returned
Fallback when VIES is downCached result
AUAustralia
SourceABR (Australian Business Register)
Returns namereturned
Returns addressreturned
Consultation #not returned
Fallback when VIES is downCached result

* Available when the request includes a requester VAT number from the same system: EU for an EU number, UK for a UK number.

† Germany and Spain publish no company data through VIES; see the full coverage table.

The same check in cURL and Node

Both return the same JSON envelope. The SDK wraps it in { data, error } and types every field.

curl -H "Authorization: Bearer avat_live_..." \
  "https://api.avatcado.com/v1/validate?vat_number=NL123456789B01"
import Avatcado from '@avatcado/node';

const avatcado = new Avatcado('avat_live_...');
const { data, error } = await avatcado.vat.validate({
  vatNumber: 'NL123456789B01',
});

if (error) {
  console.error(`${error.code}: ${error.message}`);
} else {
  console.log(data.data.valid, data.data.company?.name);
}

REST and JSON

JSON over HTTPS with snake_case fields. Every response uses the same { data, meta } or { error, meta } envelope.

Typed SDKs

@avatcado/node for TypeScript and avatcado on PyPI. Full type definitions and autocomplete. OpenAPI spec for everything else.

Structured errors

Every error returns a machine-readable code, a human-readable message, and a docs_url linking to the fix.

Hosting, data and uptime

API in Frankfurt

The API runs in an EU region (Frankfurt).

GDPR-clean

No third-party tracking on API requests. Validation history retained while your account is active. Full data export available anytime.

99.9% uptime target

Monitored continuously. When VIES cannot answer for a member state with an open national register, Avatcado queries that register on Pro and Business plans. In other upstream outages it can serve the most recent stored result for that number, whatever its age. With no stored result, the API can return a 503 that does not count against your quota.

Checkout and account creation

Two places to check a VAT number, with a guide for each.

Billing

Validate at checkout, before the invoice

Check the customer's VAT number before you decide between charging VAT and applying the reverse charge. Store the result, its timestamp, and any consultation number with the invoice as evidence of the check.

  • SaaS checkout flows
  • Subscription billing
  • Stripe and Mollie integrations
CRM & Onboarding

Clean account data from the first record

Mainstream CRMs like Salesforce and HubSpot do not validate VAT numbers out of the box. Validate when an account is created and write the registered company name back to the record. Catch bad data before it reaches invoices or ERP syncs.

  • Salesforce account creation
  • HubSpot contact enrichment
  • Partner and vendor onboarding

Start validating in under 2 minutes

npm i @avatcado/node · free 500 validations/month