Alpha testing: all current functionality is free while VAT Engine is in active development

Dated VAT rate lookup

VAT rates API

VAT Engine normalizes reviewed TEDB VAT data into a developer-friendly rate model with stable tax-class identifiers. Approved source-supported versions take precedence for their covered dates, while older imported windows remain clearly legacy.

What this helps you do

Resolve a rate with the country, product context, and date that matter to the transaction instead of relying on an undated spreadsheet.

  • Historical lookup uses approved source-supported coverage where available; older imported windows remain legacy evidence and do not by themselves prove legal applicability.
  • Curated tax classes such as books, food, accommodation, and standard goods.
  • TEDB source capture with human review and immutable approval history.
  • The public rate-lookup and exact-replay endpoints do not accept caller-selected rate-data or calculator versions.

How to use it well

Choose the jurisdiction first

A rate lookup begins with the country whose VAT rules apply, not merely the buyer’s address or a default storefront setting.

Make the product assumption explicit

Select a reviewed tax class rather than assuming every sale uses the standard rate.

Ask for the right date

Pass the supply date for historical transactions, refunds, corrections, and imports instead of silently using the current rate.

Look up a rate for a known product assumption

An ERP import already has a reviewed country and tax class. Use a dated lookup to obtain the matching recorded rate instead of copying a percentage from a homepage.

  1. Resolve the tax class first. A product name or a country standard rate does not establish reduced-rate eligibility.
  2. Call the rates endpoint from your server with a full or read-only API key and an explicit at date.
  3. Retain the returned basis points and window with the request. Review coverage errors rather than substituting an unrelated rate.
GET /v1/vat/rates?country=DE&tax_class_id=standard&at=2026-01-28
X-API-Key: YOUR_API_KEY

For example, rate_bps: 1900 represents 19%. Window dates must be interpreted with the reviewed-versus-legacy evidence boundary, rather than assumed to prove a legal start date.

Read the rate response and date rules