Common Transit Convention Traders API end-to-end service guide
This guide explains how you can use our new Common Transit Convention (CTC) Traders API with your software. The API will allow your software to send and receive movement notifications and status messages to and from the New Computerised Transit System (NCTS).
In 2021, UK traders will need to move from using the NCTS XML API to the new CTC Traders API.
Come back for regular updates
We are updating this guide as we add more functionality to our API, new technical specifications and other items we hope you find useful.
Right now, goods that can move freely within the UK can move across the EU freely too. This will change after the end of the transition period on 31 December 2020. Then, those goods will be subject to duties and other charges when they enter the EU, or enter the UK from the EU.
From 2021, if UK traders want to defer paying these duties and other charges, they can move the goods under the Common Transit Convention. This will allow traders to move goods across a number of countries, without having to pay import duties every time they cross a border. They will only have to complete the paperwork and pay any duties they owe, once they reach their destination country.
The API will allow traders to send and receive arrival and departure notifications to customs and border offices.
Why we are creating a new CTC Traders API
Common Transit will be a key procedure for moving goods between the United Kingdom and Europe. This will mean that declaration volumes will increase significantly. In order to make sure we provide a reliable and fast service we are introducing the new CTC Traders API to replace the current NCTS XML API.
Changes that come with the new CTC Traders API
The table below gives you a brief outline of how the new API uses different coding, compared to the existing NCTS XML API.
|Activity||NCTS XML API||CTC Traders API|
|Submit Arrival Notification (IE007)||SOAP authorisation (include username and password in clear text)||Government Gateway authorisation (OAuth 2.0 token)|
|Create action||SOAP wrapper, with embedded instruction||RESTful interface, action inferred from the URL|
|POST API Payload||SOAP with EDIFACT body||Information Exchange message (IE) XML|
|GET API Payload||SOAP with EDIFACT body||JSON and IE XML|