Common Transit Convention Traders API end-to-end service guide
This guide explains how to use the 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).
At the end of March 2021, you will be able to use the new CTC Traders API instead of the NCTS XML API channel for Common Transit arrivals and departures to and from Great Britain (GB), ie England, Scotland, Wales.
For timescales, see the CTC Roadmap.
We are updating this guide as we add more functionality to our API, new technical specifications.
The Common Transit Convention allows traders to move goods across CTC member states without paying import duties at every border they cross.
Under the agreement, CTC member countries only need to pay duties in the country of destination.
All goods will be subject to duties and other charges when they enter the EU, or enter the UK from the EU.
The API allows traders to send and receive arrival and departure notifications for CTC movements.
Replacing the NCTS XML API
Volumes of Common Transit movements are expected to increase significantly now that the UK is no longer part of the European Union. The current NCTS XML API channel needs to change to cope with this forecasted increase.
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.
If you have never used the NCTS XML API channel, you’ll only need to refer to the new CTC Traders API descriptions.
Comparison between the existing and the new API
The table shows 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 (includes 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|