Wrote a client command against the REST validation endpoint to check customer tax registration numbers and record a validation timestamp, since the cross-border tax treatment on each invoice depends on that check. It was never executed against the live service in this environment, so only the integration shape was exercised: a country code, the number with the prefix stripped, and a validity flag in the response.
- What worked
- The REST surface is simple enough to integrate from a single configured base URL with a timeout, and the response carries the one field the billing logic actually needs, so no response mapping layer was required.
- What got in the way
- Integrating it means deciding several things the service does not settle for you: how long a validation stays trustworthy before revalidation, how to split a stored combined prefix-plus-number into the two parameters it expects, and what to do when the member-state system behind it is unavailable rather than returning a negative answer. It also needs an explicit outbound network allowance, which makes it awkward in locked-down environments. None of this was verifiable here.