• Register
• Sign in

 

This version is in beta - expect some breaking changes.

CTC Traders API

Available in Sandbox	Yes
Sandbox base URL	https://test-api.service.hmrc.gov.uk
Available in Production	No

Overview

This API will allow you to send departure and arrival movement notifications to the New Computerised Transit System (NCTS). It will also let you retrieve messages sent from the offices of departure and destination.

The API is presently deployed to the sandbox without the endpoints being enabled. We will be re-releasing the API, with working arrivals endpoints soon.

Further details of the User Restricted Authentication are given on the Authorisation page.

For more information about how to develop your own client applications, including example clients for this API, see Tutorials.

Versioning

When an API changes in a way that is backwards-incompatible, we increase the version number of the API. See our reference guide for more on versioning.

Errors

Here is the list error codes that we will keep updating. We use standard HTTP status codes to show whether an API request has succeeded or not:

POST

400 BadRequest: If XML message is invalid

401 Unauthorized: If client passes invalid auth credentials

403 Forbidden: If supplied auth token doesn't contain valid enrolment

404 Not Found: If no object with specified ID found in database

415 Unsupported Media Type: If the client specified an invalid Content-Type header

500 Internal Server Error: If exception in code occurs

501 Not Implemented: If user attempts to POST a message and the message type isn't currently supported

PUT

400 BadRequest: If XML message is invalid

401 Unauthorized: If client passes invalid auth credentials

403 Forbidden: If supplied auth token doesn't contain valid enrolment

404 Not Found: If no object with specified ID found in database

415 Unsupported Media Type: If the client specified an invalid Content-Type header

500 Internal Server Error: If exception in code occurs

GET

401 Unauthorized: If client passes invalid auth credentials

403 Forbidden: If supplied auth token doesn't contain valid enrolment

404 Not Found: If no object with specified ID found in database. Or if client passes in an Accept header which contains the wrong API version number. We have only released version 1.0 of the API

415 Unsupported Media Type: If Accept header contains invalid type

500 Internal Server Error: If exception in code occurs

Errors specific to each API are shown in the Endpoints section, under Response. See our reference guide for more on errors.

Skip to main content

Endpoints

/customs/transits/movements/arrivals

Pull all Movement Arrivals

GET

Pull all Movement Arrivals. Any Movement Arrivals more than 28 days old will have been archived along with their related messages. Archived movements will return an HTTP 404 Not Found status.

You will only be able to retrieve these messages if you have the correct Economic Operator Registration and Identification (EORI) number for that Movement Arrival.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Request headers

Name	Description
Accept required	Specifies the response format and the version of the API to be used. For example: application/vnd.hmrc.v1.0+json
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 200 (OK)

{
     "arrivals":
       [
        {
          "arrival": "/customs/transits/movements/arrivals/123",
          "created": "2020-03-20",
          "updated": "2020-03-20",
          "movementReferenceNumber":"MRN",
          "status": "arrival notification received",
          "messages": "/customs/transits/movements/arrivals/123/messages"
        },
        {
          "arrival": "/customs/transits/movements/arrivals/987",
          "created": "2020-03-28",
          "updated": "2020-03-28",
          "movementReferenceNumber":"MRN",
          "status", "unloading permissions received",
          "messages": "/customs/transits/movements/arrivals/987/messages"
        }
       ]
}

<IE007>....</IE007>

Error scenarios

Scenario	HTTP status	Code
The accept header is missing or invalid	406 (Not Acceptable)	ACCEPT_HEADER_INVALID

For error scenarios that are common across all APIs, and for error formats, see our reference guide.

Close section

Send an Arrival Notification message

POST

Send a notification to let the Office of Destination know that the goods have arrived. This notification will be sent when the goods reach their final destination. It is also called an E_ARR_NOT (IE007).

The location header in the response will contain a URI and arrival ID for the Arrival Notification. This will allow you to get the message status.

If the user is not enrolled for an Economic Operator Registration and Identification number, they will receive an HTTP 403 Forbidden status.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Request headers

Name	Description
Content-Type required	Specifies the format of the request body, which must be XML. For example: application/xml
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response headers

Name	Description
Location required	The URI to get the Arrival Notification, including an arrival ID and message ID For example: /customs/transits/movements/arrivals/123456/messages/1

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 202 (Accepted)

<IE007>
</IE007>

Close section

/customs/transits/movements/arrivals/{arrivalId}

Pull a Movement Arrival for an arrival ID

GET

Pull a specific Movement Arrival. Any Movement Arrivals more than 28 days old will be haven archived along with their related messages. Archived movements will return an HTTP 404 Not Found status.

You will only be able to retrieve these messages if you have the correct Economic Operator Registration and Identification (EORI) number for that Movement Arrival.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Path parameters

Name	Description
arrivalId string required	The arrival ID specifying the arrival to return For example: 1

Request headers

Name	Description
Accept required	Specifies the response format and the version of the API to be used. For example: application/vnd.hmrc.v1.0+json
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 200 (OK)

{
  "arrival": "/customs/transits/movements/arrivals/123",
  "created": "2020-03-20",
  "updated": "2020-03-20",
  "movementReferenceNumber":"MRN",
  "status", "arrival notification received",
  "messages": "/customs/transits/movements/arrivals/123/messages"
}

Error scenarios

Scenario	HTTP status	Code
The accept header is missing or invalid	406 (Not Acceptable)	ACCEPT_HEADER_INVALID

For error scenarios that are common across all APIs, and for error formats, see our reference guide.

Close section

Resubmit an Arrival Notification

PUT

Resubmit an Arrival Notification to let the Office of Destination know that the goods have arrived. This message will be sent when the goods reach their final destination. It is also called an E_ARR_NOT (IE007).

The location header in the response will contain an arrival ID for the Arrival Notification. This will allow you to get the message status.

If the user is not enrolled for an Economic Operator Registration and Identification number, they will receive an HTTP 403 Forbidden status.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Path parameters

Name	Description
arrivalId string required	The arrival ID specifying the arrival to return For example: 1

Request headers

Name	Description
Content-Type required	Specifies the format of the request body, which must be XML. For example: application/xml
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response headers

Name	Description
Location required	The URI to retrieve the Arrival Notification, including arrival ID For example: /customs/transits/movements/arrivals/{arrivalId}

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 202 (Accepted)

Close section

/customs/transits/movements/arrivals/{arrivalId}/messages

Pull all messages that relate to a Movement Arrival

GET

Pull all the messages to do with a Movement Arrival. Any Movement Arrivals more than 28 days old will have been archived along with their related messages. Archived movements will return an HTTP 404 Not Found status.

You will only be able to retrieve these messages if you have the correct Economic Operator Registration and Identification (EORI) number for that Movement Arrival.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Path parameters

Name	Description
arrivalId string required	The arrival ID specifying the arrival to return For example: 1

Request headers

Name	Description
Accept required	Specifies the response format and the version of the API to be used. For example: application/vnd.hmrc.v1.0+json
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 200 (OK)

{
    "arrival": "/customs/transits/movements/arrivals/123",
    "created": "2020-03-20",
    "updated": "2020-03-20",
    "movementReferenceNumber":"MRN",
    "status", "Arrival Notification received"
    "messages": [
        {
            "message": "/customs/transits/movements/arrivals/1234/messages/456"
            "received": "2020-01-01",
            "body": "<CC025A>...</CC025A>"
        },
        {
            "message": "/customs/transits/movements/arrivals/1234/messages/789"
            "received": "2020-01-02",
            "body": "<CC043A>...</CC043A>"
        }
    ]
}

Error scenarios

Scenario	HTTP status	Code
The accept header is missing or invalid	406 (Not Acceptable)	ACCEPT_HEADER_INVALID

For error scenarios that are common across all APIs, and for error formats, see our reference guide.

Close section

Send a message related to an Arrival Movement

POST

Send a message to the Office of Destination. For example, an Unloading Remarks message, otherwise known as E_ULD_REM (IE044), to let them know that the goods have been unloaded.

If the user is not enrolled for an Economic Operator Registration and Identification number, they will receive an HTTP 403 Forbidden status.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Path parameters

Name	Description
arrivalId string required	The arrival ID specifying the arrival to return For example: 1

Request headers

Name	Description
Content-Type required	Specifies the format of the request body, which must be XML. For example: application/xml
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response headers

Name	Description
Location required	The URI to retrieve the Arrival Notification, including arrival ID For example: /customs/transits/movements/arrivals/123456/messages

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 202 (Accepted)

<IE044>...</IE044>

Close section

/customs/transits/movements/arrivals/{arrivalId}/messages/{messageId}

Pull a message relating to a Movement Arrival and message ID

GET

Pull all messages relating to a specific Movement Arrival and message ID. For example, this could include messages about route diversions or unloading permissions. Any Movement Arrivals more than 28 days old will have been archived along with their related messages. Archived movements will return an HTTP 404 Not Found status.

You will only be able to retrieve these messages if you have the correct Economic Operator Registration and Identification (EORI) number for that Movement Arrival.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Path parameters

Name	Description
arrivalId string required	The arrival ID specifying the arrival to return For example: 1
messageId string required	The message ID specifying the message to return For example: 1

Request headers

Name	Description
Accept required	Specifies the response format and the version of the API to be used. For example: application/vnd.hmrc.v1.0+json
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 200 (OK)

{
  date: "2020-12-30",
  body: "<CC058A>....</CC058A>"
}

Error scenarios

Scenario	HTTP status	Code
The accept header is missing or invalid	406 (Not Acceptable)	ACCEPT_HEADER_INVALID

For error scenarios that are common across all APIs, and for error formats, see our reference guide.

Close section

/customs/transits/movements/departures

Pull all Movement Departures

GET

Pull all Movement Departures sent to the Office of Departures within 28 days of the goods being released at their final destination. Any Movement more than 28 days old will have been archived along with their related messages. Archived Movements will return an HTTP 404 Not Found status.

You will only be able to retrieve these messages if you have the correct Economic Operator Registration and Identification (EORI) number for that Movement Arrival.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Request headers

Name	Description
Accept required	Specifies the response format and the version of the API to be used. For example: application/vnd.hmrc.v1.0+json
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 200 (OK)

{
   "departures":[
      {
        "date": "2021-01-15",
         "body":"<IE015>....</IE015>"
      },
      {
        "date": "2021-01-16",
         "body":"<IE015>....</IE015>"
      }
   ]
}

Error scenarios

Scenario	HTTP status	Code
The accept header is missing or invalid	406 (Not Acceptable)	ACCEPT_HEADER_INVALID

For error scenarios that are common across all APIs, and for error formats, see our reference guide.

Close section

Send a Declaration Data message

POST

Send a Declaration Data message, to let the Office of Destination know that the goods are on their way. This notification will be sent when the goods leave the Office of Departure. It is also called an E_DEC_DAT (IE015).

The location header in the response will contain a URI and departure ID for the Declaration Data. This will allow you to retrieve the submission status.

If the user is not enrolled for an EORI number, they will receive an HTTP Forbidden Status.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Request headers

Name	Description
Content-Type required	Specifies the format of the request body, which must be XML. For example: application/xml
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response headers

Name	Description
Location required	The URI to retrieve the departure notification, including departure ID For example: /customs/transits/movements/departures/123456

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 202 (Accepted)

<IE015>...</IE015>

Close section

/customs/transits/movements/departures/{departureId}

Pull a Movement Departure for a departure ID

GET

Pull a specific Movement Departure which was sent to the Office of Departure within 28 days of the goods being released at their final destination. Any Movements that are more than 28 days old will have been archived. Archived notifications will be return an HTTP 404 Not Found status.

You will only be able to retrieve these messages if you have the EORI number associated with the Movement Departure.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Request headers

Name	Description
Accept required	Specifies the response format and the version of the API to be used. For example: application/vnd.hmrc.v1.0+json
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response headers

Name	Description
SubmissionStatus required	The status of the notification submission, either Pending or Success For example: Pending

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 200 (OK)

<IE015></IE015>

{
  "date": "2028-01-15",
   "body":"<IE015>....</IE015>"
}

Error scenarios

Scenario	HTTP status	Code
The accept header is missing or invalid	406 (Not Acceptable)	ACCEPT_HEADER_INVALID

For error scenarios that are common across all APIs, and for error formats, see our reference guide.

Close section

/customs/transits/movements/departures/{departureId}/messages

Pull all messages relating to a Movement Departure

GET

Pull all messages sent within 28 days of the goods being released relating to a Movement Departure. Any Movements that are more than 28 days old will have been archived. Archived notifications will be return an HTTP 404 Not Found status.

You will only be able to retrieve these messages if you have the EORI number associated with the Movement Departure.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Request headers

Name	Description
Accept required	Specifies the response format and the version of the API to be used. For example: application/vnd.hmrc.v1.0+json
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 200 (OK)

{
   "messages":[
      {
         "date":"2020-12-31",
         "body":"<CC0XXA>....</CC0XXA>"
      },
      {
         "date":"2020-12-30",
         "body":"<CC0XXA>....</CC0XXA>"
      }
   ]
}

Error scenarios

Scenario	HTTP status	Code
The accept header is missing or invalid	406 (Not Acceptable)	ACCEPT_HEADER_INVALID

For error scenarios that are common across all APIs, and for error formats, see our reference guide.

Close section

Send a message related to a Movement Departure

POST

Send a message to the Office of Destination.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Request headers

Name	Description
Content-Type required	Specifies the format of the request body, which must be XML. For example: application/xml
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response headers

Name	Description
Location required	The URI to retrieve the Departure Notification, including arrival ID For example: /customs/transits/movements/departures/123456/messages

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 202 (Accepted)

<IE0XX>...</IE0XX>

Close section

/customs/transits/movements/departures/{departureId}/messages/{messageId}

Pull a message relating to a Movement Departure and message ID

GET

Pull all messages relating to a specific Movement Departure and message ID. For example, this could include declaration rejected or Movement Reference Number (MRN) allocated messages. Any messages more than 28 days old will be archived. Archived notifications will be return an HTTP 404 Not Found status.

You will only be able to retrieve these messages if you have the EORI number associated with the Movement Departure.

Authorisation

This endpoint is user-restricted and requires an Authorization header containing an OAuth 2.0 Bearer Token with the common-transit-convention-traders scope.

Request headers

Name	Description
Accept required	Specifies the response format and the version of the API to be used. For example: application/vnd.hmrc.v1.0+json
Authorization required	An OAuth 2.0 Bearer Token with the common-transit-convention-traders scope. For example: Bearer bb7fed3fe10dd235a2ccda3d50fb

See also fraud prevention for other request headers which will become mandatory.

Response

HTTP status: 200 (OK)

{
   "date":"2020-12-30",
   "body":"<CC0XXA>....</CC0XXA>"
}

Error scenarios

Scenario	HTTP status	Code
The accept header is missing or invalid	406 (Not Acceptable)	ACCEPT_HEADER_INVALID

For error scenarios that are common across all APIs, and for error formats, see our reference guide.

Close section

Skip to main content

Get help with this page. Get help with this page.