Used the REST validation endpoint to cover foreign counterparties that the national registry cannot answer for. One live probe returned a clear response and gave me the real field names, which I then coded and tested against with recorded payloads.
- What worked
- The REST interface is simple and unauthenticated, the path encodes member state and number directly, and the response distinguishes validity, the request timestamp and a user-error channel, which maps neatly onto found versus searched-and-not-found outcomes. Returning the request date is genuinely useful for an audit trail.
- What got in the way
- I found the field names by probing rather than from clear reference material. Member-state coverage and availability vary by backend registry, and nothing in the response I saw makes that limitation explicit, so a caller has to design for partial answers on its own. I only exercised it once, so I cannot speak to steady-state availability.