CITWebServices
The following operations are supported. For a formal definition, please review the Service Description.
- AddCITWaybill
- AddCITWaybill2018
- AddCITWaybillODO
- AddCITWaybillWithConsignor
- AddCPTDistributionData
- AddClientWaybill
- AddClientWaybillWithCollectionRequest
- AddClientWaybillWithConsignor
- AddClientWaybillWithConsignorAlt
- AddClientWaybillWithSuburbValidation
- AddCollectionRequest
- AddCollectionRequestWithVehicleSize
- AddDURDistributionData
- AddDeliveryExceptionAction
- AddInHouseParcel
- AddInhouseWaybill
- AddJNBDistributionData
- AddJNBDistributionDataString
- AddNewEWaybillInHouse
- AddTrackingDetails
- AddTrackingDetailsPargo
- AddWaybillAndCollectionWithVehicleSize
- AddWaybillBatchWithAddress
- CapturedWaybillTrackingDetails
- CapturedWaybillTrackingDetailsDataset
- CapturedWaybillTrackingDetailsWithTimeDataset
- ChangeClientWaybillDeliveryAddress
- CreateCredentials
- DeleteClientWaybill
- GetAddressDetailsIntOnlyXML
- GetAddressDetailsXML
- GetAddressDetailsXMLNoPartial
- GetAddressDetailsXMLWithErrorLogging
- GetAddressFromSubId
- GetAddressValidationXML
- GetCITQuote
- GetCITQuoteBySubId
- GetCITQuoteChargeODO
- GetCITQuoteChargeOnlyBySubId
- GetCITQuoteChargeOnlyBySubIdWithSurcharges
- GetCITQuoteForPlugin
- GetCITQuoteForPluginWithDates
- GetCITQuoteForPluginWithDates_SingleService
- GetCITQuoteWithExtraSurcharges
- GetCitQuoteChargeODOManual
- GetCitQuoteChargeOnly
- GetConveyorImages
- GetCourierDailyManifestDataset
- GetCourierDailyManifestDateAndTimeDataset
- GetCourierDailyManifestDateAndTimeDatasetWithHub
- GetCourierDailyManifestWithDateAndTimeXML
- GetCourierDailyManifestWithDateAndTimeXMLWithHub
- GetCourierDailyManifestWithLinkedAccountsXML
- GetCourierDailyManifestWithPiecesDataset
- GetCourierDailyManifestWithPiecesXML
- GetCourierDailyManifestXML
- GetDailyExceptionsDataset
- GetDailyExceptionsDateTimeDataset
- GetDailyExceptionsTrackingWithAllHubs
- GetDailyExceptionsWithHubDataSet
- GetDailyExceptionsXML
- GetDailyOrderSerialNumbersDataset
- GetDailyOrderSerialNumbersXML
- GetDailyOutOnDeliveryDataset
- GetDailyOutOnDeliveryXML
- GetDailyPODTimeDateDataset
- GetDailyPODsDataset
- GetDailyPODsWithLinkedAccountsXML
- GetDailyPODsXML
- GetDeliveryQuoteXML
- GetDeliverySheetDataDataset
- GetDeliverySheetDataXML
- GetDeliverySheetSummaryDataset
- GetDeliverySheetSummaryXML
- GetFilteredSuburbAddressListDataSet
- GetFilteredSuburbAddressListXML
- GetHubManifestDetails
- GetInHousePargoDataXML
- GetInterBranchManifestDetails
- GetLabelConfiguration
- GetMultipleTrackingDataset
- GetMultipleTrackingXML
- GetNonCITExceptions
- GetNonCITExceptionsWithConsignor
- GetOrderStatusXML
- GetPODBase64XML
- GetPODWebURLDataset
- GetPODWebURLXML
- GetPargoAddressDetailsXML
- GetPargoAddressPupOrSubId
- GetRTSReport
- GetSuburbAddressListDataSet
- GetTrackingCurrentStatus
- GetTrackingDataset
- GetTrackingDatasetFromShippersReference
- GetTrackingDatasetOOD
- GetTrackingDatasetWithExtraData
- GetTrackingDetailsServiceFilter
- GetTrackingDetailsWithServiceFilter
- GetTrackingLink
- GetTrackingWaybillOnlyDataset
- GetTrackingWaybillOnlyXML
- GetTrackingWithConsigneeDetailXML
- GetTrackingWithDistributionDataXML
- GetTrackingXML
- GetTrackingXMLFromShippersReference
- GetTrackingXMLWithFormattedDateAndTime
- GetTrackingXML_City
- GetWaybillBillingActualXML
- GetWaybillBillingXML
- GetWaybillQuoteXML
- HelloWorld
- IsPargo
- Login
- PlaceMobileShopOrderDataset
- StripAccountFromField_Internal
- UpdateAndLogInHouseData
- UpdateAndLogPluginData
- UpdateInHouseSubmission
- UpdateInhousePieces
- UpdateMultipleTrackingTransferred
- UpdateWaybillPargoData
This web service does not conform to WS-I Basic Profile v1.1.
Please examine each of the normative statement violations below. Follow the recommendations to remedy it, or add setting to the <webServices> config section to turn off BP 1.1 conformance warnings for the entire vroot.
To turn off BP 1.1 conformance warnings for the entire vroot remove the 'BP1.1' value from the <conformanceWarnings> section of the configuration file of your application:
<configuration>
<system.web>
<webServices>
<conformanceWarnings>
<remove name='BasicProfile1_1'/>
</conformanceWarnings>
</webServices>
</system.web>
</configuration>
R2210: If a document-literal binding in a DESCRIPTION does not specify the parts attribute on a soapbind:body element, the corresponding abstract wsdl:message MUST define zero or one wsdl:parts.
- Operation 'AddJNBDistributionData' on binding 'CITWebServicesSoap' from namespace 'http://citjnb.co.za/citwebservices/'.
Recommendation: For Document-literal bindings, the Profile requires that at most one part, abstractly defined with the element attribute, be serialized into the soap:Body element. When using a Bare parameter style, a conformant method must have at most one parameter.
For more details on Basic Profile Version 1.1, see the Basic Profile Specification.