VAT lookup and company data API.
Connect the number to the company.

COMPANY SEARCH, VAT LOOKUP & EIN MATCHING

Start with the information you already have.

A company data API lets software search for a business and retrieve its attributes. VATFind focuses on legal-company identity and business identifiers: a company name can lead to an available VAT number, while a supplied VAT number or EIN can lead back to a company record.

RESPONSE DATA DICTIONARY

Which company data fields does the API return?

These are the fields in VATFind’s public Company schema. Search results return company objects in data[]; a matched identifier check can include one in company. Required properties describe the response shape, not a guarantee that every identifier array contains a value.

Additional attributes where available

Identifier checks also return format_status, registry_match_status, tax_authority_status, company_legal_status, evidence, warnings and credits_used. Keep these alongside the check ID so your team can explain a result later.

const response = await fetch("https://vatfind.com/v1/checks", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.VATFIND_API_KEY}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID()
  },
  body: JSON.stringify({
    identifier_type: "vat_number",
    identifier: "GB123456789",
    country_code: "GB"
  })
});

const check = await response.json();
if (!response.ok) throw new Error(check.detail);
console.log(check.registry_match_status);

{
  "identifier_type": "vat_number",
  "identifier": "GB123456789",
  "country_code": "GB",
  "client_reference": "invoice-1048"
}

Search, check and monitor through one REST interface

CHOOSING A VAT API

VAT number lookup and VAT validation answer different questions.

VAT lookup identifies the company associated with a number, or finds an available number from a company name. Live VAT validation asks a tax authority whether a registration is valid at the time of the request. Choose the service by the evidence your application needs.

• Keep ambiguous matches in a review queue.
• Record source outages separately from completed no-matches.
• Use company-record monitoring when you need scheduled rechecks and signed webhook events.