What the TSS API actually is
The TSS API is a JSON-based submission channel to the Trader Support Service. It accepts the same declarations the portal accepts, from a system rather than a human. TSS charges nothing for access and the endpoints are the same for every registered trader.
Field mapping is where projects live or die
Every declaration field must be sourced from an authoritative system. If a value appears in two places, decide which one wins before writing any code. The TSS API integration guide sets out the sequence: register, locate fields, map to TSS specifications, build, test, validate failure paths, run in parallel.
Build a test environment first
Do not integrate against production. Build in the dedicated environment TSS provides, run the full lifecycle including rejections, and only then plan cutover.
Rejection handling is the real design
Success cases are easy. Rejections need a defined path: which system logs the failure, which team sees it, what the retry pattern is, and how long a submission can sit in an error state before it violates a deadline.
Progressive assembly
The API supports adding information incrementally as consignment details arrive. Model that in your queue design; do not treat every declaration as a single atomic post.
Run both channels during migration
Parallel running is not optional. Keep the portal live for the same movements until API submissions have produced clean results across a full month cycle.
See a working TSS API integration inside iCustoms. Watch a demo.
Top comments (0)