The number of service requests related to direct message exchange has changed. In future, customers can send more service requests within a given time than previously. There are new restrictions in the total number of service requests received by Customs related to direct message exchange.
The processing of service requests per customer connected to the service is restricted as follows (IntermediaryBusinessID):
- Upload: The service processes, at one-second intervals, no more than three Upload requests.
- UploadAttachment: The service processes, at one-second intervals, no more than three UploadAttachment requests.
- DownloadList: The service processes, at five-minute intervals, no more than one DownloadList request.
- Download: The service processes, at one-second intervals, no more than five Download requests.
- CheckConnectivity: The service processes, at one-second intervals, no more than one CheckConnectivity request.
When the customer starts to use the Message Notification Service, the customer can send DownloadList service requests once an hour at the most.
Furthermore, the total number of joint message exchange messages for all customers is restricted as follows:
- Upload: The service processes no more than 20 customs declarations per second.
- UploadAttachment: The service processes no more than 20 attachments per second.
- DownloadList: The service processes no more than 10 requests for decision lists ready for retrieval per second.
- Download: The service processes no more than 100 clearance decision retrievals per second.
DownloadList and CheckConnectivity requests that exceed the above thresholds are rejected. However, enquiries regarding Upload, UploadAttachment and DownLoad will not be rejected outright, but rather they are “buffered”, when the customer has sent requests that exceed the threshold. In that case, the SOAP request that Customs received through the TCP session, is left queuing for processing. An Upload request or Download request that has been placed in a queue is only rejected if it has not been processed before the https connection timeout.
More information by email from TH.DirectMessageExchange(at)tulli.fi
