FAQ #
1.What is CRF? #
CALISTA Regulatory Filing (CRF) is a centralised global trade platform that facilitates regulatory submission to customs nodes globally. CRF is offered as a Software-as-a-Service and is currently connected to about 60 nodes.
2. What is the CRF Singapore API Service? #
The CRF Singapore API Service allows customers to integrate with our platform to provide trade data for the purposes of regulatory filing to Singapore Customs via TradeWeb.
3. What is TradeWeb? #
TradeWeb is one of the accredited web-based front-end application which connects to the TradeNet® for regulatory submissions to Singapore Customs for clearance of goods.
4. What is TradeNet? #
TradeNet is Singapore’s National Single Window for trade declaration.
TradeWeb.
5. How do I submit to Singapore Customs via TradeWeb? #
Customers may submit permit filings straight to Singapore Customs without any intervention on the TradeWeb front-end system fulfilling all mandatory data requirements.
6. What types of regulatory submissions are catered through the API submissions? #
• Inward Payment
• Inward Non-Payment
• Outward
• Transshipment
• Certificate of Origin
7. How can I test the submissions? #
There is an online swagger portal available to test the API. The Swagger portal will allow the test data to be sent to our trial system. To use the swagger portal, guest login is required, kindly use the credentials provided by us for your testing. If you have queries, kindly approach the GeTS representative with you queries. Provided below are details for testing.
a. Once logged into Swagger menu. All the API will be shown.
b. The API which needs to be tested can be expanded and inputs should be provided.
c. Once execution is completed, appropriate responses will be returned.
8. What are the data requirements and how do I prepare the data for submission? #
Please refer to the specifications and samples provided under Section 4 above for details.
9. How long would the submission take, and will there be an acknowledgement? #
After an API submission is done, an acknowledgement will be provided to confirm that the transaction has been created or has any errors within a minute. For subsequent messages from TradeWeb, the status enquiry API needs to be invoked to retrieve all these messages. The time required to receive all messages from TradeWeb is typically within 10 minutes.
10. What responses will I get? #
Only acknowledgements are provided. Approvals are simulated in the test environment for understanding of the response message structure. Actual responses on approvals/rejections will be available only in the Production environment.
11. How long before I get a response? #
This is dependent on the TradeNet system. As soon as approvals are rejections are given/sent back, the info will be relayed back immediately. The status enquiry API needs to be invoked to retrieve all response messages. The time required for responses from TradeNet is dependent on various factors in terms of automated processing or additional screening time required by Customs.
12. Do I need to access TradeWeb to perform submissions to customs? #
No. Submissions may be routed to TradeNet if all mandatory data requirements are fulfilled.
13. What are the pre-requisites for using the CRF Singapore API Service? #
For a submission a TradeWeb account is required which is required to be tied to a Tradenet account. This can be setup as part of the registration and on-boarding process. We will help to set this up as part of the on-boarding and setup for Production / Live transactions.
14. How much is the Singapore CRF API Service and how do I sign up? #
There are various subscription packages available to suit your needs, kindly fill up the Enquire / Sign-Up form on the GeTS web page and a GeTS representative will reach out to you soon.
ACE Air Response #
| JSON Fields | Default | Description | M/C/O |
|---|---|---|---|
Response Date |
M |
||
Response Time |
M |
||
Master Level |
MAWB Number for AIR/ACAS (No response message; response message is indicated on the HBL level) only to identify MAWB number |
M |
English 
Chinese (China) 
Chinese (Hong Kong) 
French 
German 
Italian 
Japanese 
Portuguese 
Romanian 
Slovak 
Spanish (Colombia) 
Spanish (Chile) 
Spanish (Ecuador) 
Spanish (Mexico) 