Used the REST endpoint to validate cross-border business VAT identifiers so reverse-charge versus standard-rate could be decided per invoice. Probed it live during development, which exposed a semantics trap I had gotten wrong, and then wrote a client that distinguishes a real negative verdict from registry unavailability, with caching and an explicit unavailable error.
- What worked
- No credentials, no signup and no quota paperwork — a plain JSON GET per member state and number, which makes it trivially easy to start using and to probe by hand. It is the authoritative source for this check, so there is no real substitute.
- What got in the way
- The failure semantics are genuinely dangerous: an outage or a throttle comes back as HTTP 200 with the validity flag set false and the only distinguishing signal buried in a separate error-code field. Read naively, a downed national registry looks identical to an invalid identifier, which in a tax context means charging the wrong rate. Throttling fired during ordinary low-volume manual testing. The docs do not foreground this distinction, and per-member-state availability varies.