File Format
The file you submit to ONESOURCE must be in XML. This Web Services Guide contains a template that can be used for successfully creating those files.
Below is a sample SOAP 1.1 request.
The placeholders (string) must be replaced with actual values.
POST /DTSwebservice/dtswebservice.asmx HTTP/1.1
Host: dts.integrationpoint.net
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://integrationpoint.com/DPSIntegratedSearch"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<DPSIntegratedSearch xmlns="http://integrationpoint.com/">
<company>string</company>
<username>string</username>
<password>string</password>
<loggedInUser>string</loggedInUser>
<companyId>string</companyId>
<SearchType>string</SearchType>
<settingsDescription>string</settingsDescription>
<name>string</name>
<address>string</address>
<city>string</city>
<countryCode>string</countryCode>
<countryStateCode>string</countryStateCode>
<postalCode>string</postalCode>
<dtsSearchFlag>string</dtsSearchFlag>
<dtsLastValidatedDate>string</dtsLastValidatedDate>
<dtsOverride>string</dtsOverride>
<dtsOverrideDate>string</dtsOverrideDate>
<SearchRefNum>string</SearchRefNum>
<CompanySync>string</CompanySync>
<EntityType>string</EntityType>
</DPSIntegratedSearch>
</soap:Body>
</soap:Envelope>
Below is a sample SOAP 1.2 request.
The placeholders (string) must be replaced with actual values.
POST /DTSwebservice/dtswebservice.asmx HTTP/1.1
Host: dts.integrationpoint.net
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<DPSIntegratedSearch xmlns="http://integrationpoint.com/">
<company>string</company>
<username>string</username>
<password>string</password>
<loggedInUser>string</loggedInUser>
<companyId>string</companyId>
<SearchType>string</SearchType>
<settingsDescription>string</settingsDescription>
<name>string</name>
<address>string</address>
<city>string</city>
<countryCode>string</countryCode>
<countryStateCode>string</countryStateCode>
<postalCode>string</postalCode>
<dtsSearchFlag>string</dtsSearchFlag>
<dtsLastValidatedDate>string</dtsLastValidatedDate>
<dtsOverride>string</dtsOverride>
<dtsOverrideDate>string</dtsOverrideDate>
<SearchRefNum>string</SearchRefNum>
<CompanySync>string</CompanySync>
<EntityType>string</EntityType>
</DPSIntegratedSearch>
</soap12:Body>
</soap12:Envelope>
SOAP 1.2 (DPSIntegratedSearchV2)
Below is a sample SOAP 1.2 (DPSIntegratedSearchV2) request.
The placeholders (string) must be replaced with actual values.
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<tns:DPSIntegratedSearchV2 xmlns:tns="http://integrationpoint.com/" xmlns="http://integrationpoint.com/">
<tns:company>string</tns:company>
<tns:username>string</tns:username>
<tns:password>string</tns:password>
<tns:loggedInUser>string</tns:loggedInUser>
<tns:companyId>string</tns:companyId>
<tns:SearchType>string</tns:SearchType>
<tns:settingsDescription>string</tns:settingsDescription>
<tns:name>string</tns:name>
<tns:address>string</tns:address>
<tns:city/>string</tns:city/>
<tns:countryCode>string</tns:countryCode>
<tns:countryStateCode>string</tns:countryStateCode>
<tns:postalCode/>string</tns:postalCode/>
<tns:dtsSearchFlag>string</tns:dtsSearchFlag>
<tns:dtsLastValidatedDate>string</tns:dtsLastValidatedDate>
<tns:dtsOverride>string</tns:dtsOverride>
<tns:SearchRefNum/>string</tns:SearchRefNum/>
<tns:dtsOverrideDate>string</tns:dtsOverrideDate>
<tns:CompanySync>string</tns:CompanySync>
<tns:EntityType/>string</tns:EntityType/>
<tns:addresses>
<tns:AddressData>
<tns:Id>string</tns:Id>
<tns:Name>string</tns:Name>
<tns:AddressType>string</tns:AddressType>
<tns:Address>string</tns:Address>
<tns:City>string</tns:City>
<tns:CountryCode>string</tns:CountryCode>
<tns:StateCode>string</tns:StateCode>
<tns:PostalCode>string</tns:PostalCode>
<tns:SettingsDescription>string</tns:SettingsDescription>
<tns:EntityType>string</tns:EntityType>
</tns:AddressData>
<tns:AddressData>
<tns:Id>string</tns:Id>
<tns:Name>string</tns:Name>
<tns:AddressType>string</tns:AddressType>
<tns:Address>string</tns:Address>
<tns:City>string</tns:City>
<tns:CountryCode>string</tns:CountryCode>
<tns:StateCode>string</tns:StateCode>
<tns:PostalCode>string</tns:PostalCode>
<tns:SettingsDescription>string</tns:SettingsDescription>
<tns:EntityType>string</tns:EntityType>
</tns:AddressData>
</tns:addresses>
</tns:DPSIntegratedSearchV2>
</soap:Body>
</soap:Envelope>
This webservice is able to screen not only the primary entity but also any number of related addresses within single service call. This service includes logic to synchronize screened data with a local database, based on a configuration flag (CompanySync is set to “Y”).