The Problem: No Public TRACES Endpoint
TRACES NT does not expose a public endpoint for establishment validation. It works within IMSOC for member state systems, not for POSTing a batch of codes and getting JSON back. Teams that need that functionality build or buy a layer that sits in front of the official data.
What the Request/Response Cycle Looks Like
A working implementation follows five steps: authenticate with a token, submit codes with country and activity context (single or bulk), run validation against the official TRACES EU database, receive a structured response flagging valid, invalid, delisted or mismatched codes, and persist the result to an audit trail automatically. This TRACES NT API integration flow is what the iTraces REST API implements end to end.
Authentication
Use token-based authentication with rotation rather than shared credentials. Treat tokens the way you would any other API secret: short-lived, scoped, and rotated on a schedule.
Error Semantics You Actually Need
Don't settle for a single boolean. You need distinct responses for invalid, delisted, incorrect-activity and unknown codes. Each maps to a different fix.
Bulk vs Single Requests
Support both. Nightly catalogue re-validation needs bulk; a new-supplier check triggered at data entry needs a fast single-code response.
Watch a demo to see the request and response format for yourself.
Top comments (0)