-
-1. Software redirects the user to the Government Gateway for login.
-2. Once authenticated, Government Gateway redirects back to 3rd party software.
-3. User sends an Arrival Notification.
-4. Arrival Notification message passes through the CTC API.
-5. Arrival Notification is received by the NCTS.
-6. An accepted status passes through the CTC Traders API.
-7. A message arrives at the third party software to inform the user that the Arrival Notification has been received but not yet processed.
diff --git a/source/documentation/ctc-traders-api-xsds.zip b/source/documentation/ctc-traders-api-xsds.zip
deleted file mode 100644
index 86627ce..0000000
Binary files a/source/documentation/ctc-traders-api-xsds.zip and /dev/null differ
diff --git a/source/documentation/end-to-end-happy-path.html.md.erb b/source/documentation/end-to-end-happy-path.html.md.erb
deleted file mode 100644
index 62c8fb0..0000000
--- a/source/documentation/end-to-end-happy-path.html.md.erb
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: End-to-end happy path diagram | CTC APIs End-to-End Service Guide
-weight: 4
-
----
-
-<%= partial 'partials/google_tag_manager_js' %>
-
-# End-to-end happy path
-
-Version 0.1 3rd June 2020
-***
-
-
-This diagram shows the end-to-end process of transporting goods using the Common Transit Convention API. It shows at what stage in the process each message is sent, and who each message is sent to and from.
-
-
-
-1.a Trader at departure fills in and sends a declaration notification IE015.
-
-1.b Office of departure receives declaration notification.
-
-2.a Office of departure sends an acknowledgement of declaration 1E928.
-
-2.b Trader at departure receives acknowledgement notification.
-
-3.a Office of departure sends a Movement Reference Number (MRN) IE028.
-
-3.b Trader at departure receives MRN.
-
-4.a Office of departure sends notification releasing goods for transit IE029.
-
-4.b Office of departure receives notification releasing goods for transit.
-
-5.a Office of departure sends a notification to each office in the countries the goods will pass through in transit. This does not use the CTC Traders API.
-
-5.b Office or offices of transit receive notification that goods will pass through their border.
-
-6.a Office of departure sends a notification to confirm the goods have been released for transit. This does not use the CTC Traders API.
-
-6.b Office of destination receives notification that goods are on route to their Office.
-
-7.a Office or offices of transit sends a notification to confirm goods have passed through their border. This does not use the CTC Traders API.
-
-7.b Office or offices of departure receives confirmation that goods have passed through their borders.
-
-8.a Trader at destination sends a notification to confirm that goods have arrived at their final destination IE007. This is for simplified procedure only.
-
-8.b Office of destination receives confirmation that goods have reached their final destination.
-
-9.a Office of destination sends a notification to confirm goods have reached their final destination. This does not use the CTC Traders API.
-
-9.b. Office of departure receives notification that goods have reached their final destination.
-
-10.a Office of destination sends notification that goods have passed or failed control checks. This does not use the CTC Traders API.
-
-10.b Office of departure receives notification that goods have passed or failed control checks.
-
-11.a Office of departure sends permission that the goods can be unloaded IE043.
-
-11.b Trader at destination receives unloading permission.
-
-12.a Trader at destination sends unloading remarks about the state of the goods.
-
-12.b Trader a destination receives unloading remarks.
-
-13.a Office of departure sends notification to release the goods IE025.
-
-13.b Trader at destination receives a notification that goods have been released.
-
-14.a Office of destination sends notification to confirm that the goods movement is complete IE045.
-
-14.b Trader at departure receives notification that the goods movement is complete.
diff --git a/source/documentation/get-support.html.md.erb b/source/documentation/get-support.html.md.erb
deleted file mode 100644
index 22eb66c..0000000
--- a/source/documentation/get-support.html.md.erb
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Get support and help | Common Transit Convention API end-to-end service guide
-weight: 6
----
-
-<%= partial 'partials/google_tag_manager_js' %>
-
-# Find support
-
-
-
-### Check service availability first
-
-Before you get in touch, check out whether API downtime or technical issues are the problem.
-**[Check the CTC Traders API service availability](https://api-platform-status.production.tax.service.gov.uk)**
-**[Check the NCTS platform service availability](https://www.gov.uk/government/publications/new-computerised-transit-system-ncts-web-service-availability-and-issues/new-computerised-transit-system-ncts-web-service-availability-and-issues)**
-
-### Get support
-
-If you have a general query about the CTC Traders API, you can get in touch with our Software Developer Support Team with any CTC Traders API questions and support requests. If they can't help you themselves, they’ll find the help you need. You’ll get an initial response in 2 working days.
-
-Email them to receive a form where you can add details about your requirements and questions at | Your Question | -Our Answer | -
|---|---|
| Will there be a filter on XML EORI since we could potentially have several hundred or thousands of enrolments? | -Yes, we can filter on EORI over a 28 day period but we are currently working on a more suitable filter. | -
| How long will OAuthTokens be valid for once they are issued? | -The OAuth tokens are valid for 18 months unless there’s an update and they become invalid. The session token is valid for 4 hours. After 4 hours you will need to regenerate the token. For further information go to the following auth pages on dev hub: https://developer.service.hmrc.gov.uk/api-documentation/docs/authorisation/user-restricted-endpoints | -
| How will we find out when the OAuthToken is about to become invalid? | -The token itself will tell you how long it will remain valid for. | -
| If a client revokes my access, then will the first notification I get about this be your refresh token on messages fails with 401? | -Yes our refresh token will be your first notification of this. | -
| Can Push notifications go live sooner? | -We are currently working to many priorities at present but envisage push notifications to go live around May 2021. We'll email out a formal update closer towards the time. | -
| Are movements from GB to any other transit area available or possible? For example from France to Northern Ireland in the UK? | -Yes in due course. We expect to release this functionality in May, then movements both from and to Northern Ireland will be possible | -
| Is October still the planned go live date for testing the system for real customers which consignees and consignors can use? | -The testing date you mention might be for a different project as this is not CTC related. We are making enquiries with the policy team to establish what this might refer to. For more information, please contact your Business Relationship Manager in the first instance. | -
| When we are able to test with the Trader Test service, will it provide automated responses or will we have to continue injecting our own IE messages? | -Once Trader Test is active you will get automated responses where that would be true in ‘real life’ use but also there are manual responses, which you will require support staff to initiate. Guidance on this can be found here. The manual steps are called out in the test pack. | -
| Will a user be able to use the same set of credentials for both GB and NI once CTC API is up and running? Or will they need to use two different sets of credentials? | -A single set of credentials can submit both NI and GB movements. | -
| When you refer to the IE Message IE007, is this the same as IE07? | -Yes. We have added the extra digit to ensure that IE messages work across several NCTS systems across the EU. We will be updating all document to use three digits in future but this may take some time. | -
| Is testing a session token a new step for your CTC application? | -All HMRC APIs are the same including CDS. The session token (same as the access token) is valid for 4 hours and can be refreshed, the Auth token is valid for 18 months. | -
| We are currently receiving EDIFACT responses in the legacy system. When will we start to receive XML JSON responses from the new system? For example HATEOAS JSON? | -This is already in place and you should be receiving JSON messages from the new system in the sandbox environment | -
| I understand that HMRC updated their API to accomodate NI so that we could continue to use the same business as usual service. You are now asking for us to use a new identification message of XI007 rather than GB007. How do you plan to differentiate between NI and GB movements? | -The office of destination or departure will have a GB or XI pre-fix that we will use to route the message to the correct NCTS core. | -
| When do you intend to turn off the HMRC legacy systems? | -There are no confirmed dates yet. There will be a period of dual running. We will provide ample notice once a date is set for switch off of the legacy system so you can plan ahead accordingly. However it is important to note that the legacy systems are going to become increasingly unstable with the amount of extra traffic and we expect performance to degrade. We strongly advise that you should move to the new API as soon as possible. | -
| When dealing with IE015 declaration messages, will our applications need to be authenticated as the Principal? | -To submit any message via the CTC Traders API, the application will need to be subscribed to the API on the Developer Hub and have a valid client ID and client secret. The Trader will also need to be authenticated by the Government Gateway and the application will have to include the access token as a header when the messages are submitted. | -
| Can we submit on behalf of another Principal without using their log in details or being logged in as them? | -Yes you can. Also note that the EORI on the user and IE015 do not need to match. | -
| Where can I find the latest collection of postman test script files? | -We have published these on GIT Hub which you can access here: https://github.com/hmrc/common-transit-convention-traders-postman | -
| We currently use IA prefix as the message code, are you planning to change this in the future? | -The message XML will always start with a 'CC' tag, for example Arrivals <CC007A> and end with a matching CC close tag, for example </CC015B> | -
| In addition to the current testing window of 1st to 31st March, what other facilities can we use, like test flag messages for example? | -Our sandbox environment will still be available after the transition to Production. The API will continue to be available with Trader Test service in the sandbox environment indefinitely, so that you can continue to test even after we go live. Please note that it is illegal to test in the Production environment. You must never attempt to do this. | -
| France uses a different concept of lodged and pre-lodged departures. This is called the DeltaT French system. Will CTC use the same idea and principle? | -We currently support the pre-lodged. For simplified processes it is likely to be an automatic release. | -
| Will your sandbox testing environment provide the real-life proper responses? | -Yes its a clone of live, you will receive all the messages throughout the journey and SDST will be available for support. | -
| How do we contact you if we have a specific question or issue to discuss? | -Your first port of call is emailing the Software Developer Support Team at SDSTeam@HMRC.gov.uk. If they cannot easily answer your question, they will schedule a call with our team. | -
| Will your CTC API provide me with new status messages for whole transit declarations which are submitted through the NCTS XML API. This includes messages such as GB045A for example? | -The full set of message types supported by the CTC Traders API can be found here: https://developer.service.hmrc.gov.uk/guides/common-transit-convention-traders-service-guide/documentation/xsd-reference.html#validate-arrivals-xml-from-ncts. This includes IE045 | -
| Will new messages be sent to advise that goods have progressed or are progressing through offices of transit? | -Currently no Office of Transit messages are supported though the CTC Traders API. We will look to see if they are supported through another HMRC API and get back to you. | -
| Will we be able to get status updates like the ones on the Europa page? | -We can see the value in this request and will make enquiries within HMRC to explore if this is feasible. However this may require work from multiple teams and if approved, this would be in the longer term. | -
| Can the IBFs (Inland Border Facility) see the LRNs (Local Reference Number) that the NCTS system has acknowledged as received? | -If your application has received a 202 Accepted back from the POST IE015, then it has been "accepted" by NCTS, i.e. it's on their queue for processing. You can retrieve a status of all current movements using this endpoint.
-https://developer.service.hmrc.gov.uk/api-documentation/docs/api/service/common-transit-convention-traders/1.0#_get-all-movement-departures_get_accordion -The "status" field contains the current state of the movement. -NCTS will reply with an IE928 or an IE028 to confirm the movement has been processed. You can check the individual movement status using these endpoints: -https://developer.service.hmrc.gov.uk/api-documentation/docs/api/service/common-transit-convention-traders/1.0#_get-a-movement-departure-for-a-departure-id_get_accordion -https://developer.service.hmrc.gov.uk/api-documentation/docs/api/service/common-transit-convention-traders/1.0#_get-all-messages-relating-to-a-movement-departure_get_accordion - |
-
| Will we get updates for old transit declarations which are submitted by NCTS XML API, not CTC API. We will still have many unclosed declarations and will need to get status messages for those old declarations after we shift to CTC API. Will you divert all the status messages into CTC API? Otherwise we will need to keep both structures live? | -All in-flight movements will have to be completed on the legacy NCTS SOAP XML. Legacy movements cannot be viewed on the new API. | -
| When is the IE message IE928 created? | -In most cases, directly after the IE015 has been submitted, although it depends if the movement is simplified or not. Please refer to the Technical Interface Specifications (TIS) document and the TIS appendices for all the business rules. | -