Categorise errors first
Not every rejection is the same. Some are data validation issues, some are authorisation, some are structural. Group them before you chase them.
Route by category, not by ticket
Data errors go to the operator who owns the source document. Authorisation errors go to compliance. Structural errors go to the engineering team.
Learn from repeat offenders
If the same error code keeps appearing, the fix is upstream, not in the API client. The TSS API troubleshooting guide captures the common patterns.
Keep the response payload
The JSON error response is the shortest path to the fix. Log it, link it to the declaration and make it searchable.
See how iCustoms turns TSS rejections into structured tasks — Watch a demo.
Top comments (0)