The following operations are supported. For a formal definition, please review the Service Description.

• AddDocumentAttachmentLinkToShipment
  Add Document Attachment Linkage to a Particular Shipment.
• AddEmailNotificationToCustomer
  Add an Email Status Notification to a Particular Customer.
• AddEmailNotificationToShipment
  Add an Email Status Notification to a Particular Shipment.
• AttachFileToShipment
  Attach a Document to a Particular Shipment.
• AttachFileToShipmentC
  Attach a Document to a Particular Shipment.
• CallAttachFileToShipmentByShipperRef
  Attach a Document to a Particular Shipment by Shipper Ref No
• DeleteEmailNotificationForCustomer
  Delete an Email Status Notification for a Particular Customer.
• DeleteEmailNotificationForShipment
  Delete an Email Status Notification for a Particular Shipment.
• GenerateShipmentDocument
  Generate shipment document
• GetHAWBLastPublicStatus
  Get Last Public Status of a Valid Airway Bill
• GetHAWBStatus
  Get Status of a Valid Airway Bill
• QuoteListLast30DaysByCustomer
  Get Quote List - Last 30 Days For Customer
• ShipmentInquiry
  Tracking Shipment By Housebill
• ShipmentInquiryV2
  Tracking Shipment By Ship/Quote# or Housebill
• ShipmentInquiryV3
  Tracking Shipment By Ship/Quote# or Housebill
• ShipmentList30Days
  Get Shipment List - 30 Days From Shipment Creation
• ShipmentListByRefNo
  Get Shipment List - Reference Number
• ShipmentListLast30DaysByCustomer
  Get Shipment List - Last 30 Days For Customer
• SubmitPOD
  Update POD of a Valid Airway Bill
• SubmitPODByConsolNo
  Update POD of a Valid Airway Bill
• SubmitPODByShipperRefNo
  Update POD of a Valid Airway Bill By Shipper Reference Number
• UpdateEmailNotificationForCustomer
  Update an Email Status Notification for a Particular Customer.
• UpdateEmailNotificationForShipment
  Update an Email Status Notification for a Particular Shipment.
• UpdateShipmentDetail
  Update Detail Line of Shipment
• UpdateStatus
  Update Status of a Valid Airway Bill
• UpdateStatusByConsolNo
  Update Status of a Valid Airway Bill
• UpdateStatusByShipperRefNo
  Update Status of a Valid Airway Bill By Shipper Reference Number
• UpdateStatusByShipperRefNoWithEventDT
  Update Status of a Valid Airway Bill By Shipper Reference Number
• UploadPODDocument
  Upload POD Document for a Valid AirWay Bill
• UploadPODDocumentByShipperRefNo
  Upload POD Document for a Valid AirWay Bill By Shipper Reference Number
• ValidateHAWB
  Validate WorldTrak HAWB

This web service is using http://tempuri.org/ as its default namespace.

Recommendation: Change the default namespace before the XML Web service is made public.

Each XML Web service needs a unique namespace in order for client applications to distinguish it from other services on the Web. http://tempuri.org/ is available for XML Web services that are under development, but published XML Web services should use a more permanent namespace.

Your XML Web service should be identified by a namespace that you control. For example, you can use your company's Internet domain name as part of the namespace. Although many XML Web service namespaces look like URLs, they need not point to actual resources on the Web. (XML Web service namespaces are URIs.)

For XML Web services creating using ASP.NET, the default namespace can be changed using the WebService attribute's Namespace property. The WebService attribute is an attribute applied to the class that contains the XML Web service methods. Below is a code example that sets the namespace to "http://microsoft.com/webservices/":

C#

[WebService(Namespace="http://microsoft.com/webservices/")]
public class MyWebService {
    // implementation
}

Visual Basic

<WebService(Namespace:="http://microsoft.com/webservices/")> Public Class MyWebService
    ' implementation
End Class

C++

[WebService(Namespace="http://microsoft.com/webservices/")]
public ref class MyWebService {
    // implementation
};

For more details on XML namespaces, see the W3C recommendation on Namespaces in XML.

For more details on WSDL, see the WSDL Specification.

For more details on URIs, see RFC 2396.