DataTools Kleber Method Description

Method:
DataTools.Capture.Address.Predictive.CaPaf.SearchAddress
You can use this method when you have the start of a Canadian address you wish to search against the Canada Post PAF. This method is perfect for Predictive Search rapid address capture.

Please Note:
Special conditions apply to the use of this method. This method must always be used in conjunction with the retrieve method DataTools.Capture.Address.Predictive.CaPaf.RetrieveAddress. If the retrieve method is not called, or not utilised with an appropriate retrieve ratio to searches, an auto retrieve cost will be applied to your account to ensure you do not breach the data licencing conditions.

Test:

Parameter	Value
AddressLine
ResultLimit
ReturnGroupResults
PreviousSearchRecordId
RequestId
RequestKey
DepartmentCode

Input Parameters:

Parameter	Description
AddressLine	A full or part of an address line of eg. '123 main st' or '123 mai'. The AddressLine argument can also optionally include the Municipality and Province information.
ResultLimit	A numeric value representing the maximum results to be returned. If no value supplied a default maximum of 10 results will be returned. Maximum allowed 50.
ReturnGroupResults	This option will group results together which can expanded on with additional searches.
PreviousSearchRecordId	Record ID from previous search. Only required when the ReturnGroupResults='True' option is used and the group results are returned with NextSearch='Search'. Use the Record ID from the previous search to return child results from groups.
RequestId	Optional user value to assist in linking DtRequests with DtResponses.
RequestKey	Required for user access verification. For client side script protect your Request Key by using the DataTools.Security.GenerateTemporaryRequestKey
DepartmentCode	Optional user value to allocate transaction usage by department. Limit of 50 unique Department codes per account.

Output Fields:

Field	Description
RecordId	Record ID used to retrieve further information
AddressLine	Address Line for suggestion display.
NextSearch	Returns if the result selected need to be searched again using the Search method or Retrieve method. Search is only returned of the RetrieveChildRecords is set to False.

Supported Web Service API Interfaces:

Web Service Method: ProcessQueryStringRequest (REST)

Request Format: Url QueryString, Protocols: HTTP GET, HTTPS GET, Response Formats: JSON, XML*
Example Server Path: https://customname.datatoolscloud.net.au/KleberWebService/DtKleberService.svc

Sample QueryString Request:
/ProcessQueryStringRequest?Method=DataTools.Capture.Address.Predictive.CaPaf.SearchAddress&AddressLine=&ResultLimit=&ReturnGroupResults=&PreviousSearchRecordId=&RequestId=&RequestKey=&DepartmentCode=

Sample JSON Response:
{
   "DtResponse":{
      "RequestId":"",
      "ResultCount":"1",
      "ErrorMessage":"",
      "Result":[
         {
            "RecordId":"",
            "AddressLine":"",
            "NextSearch":""
         }
      ]
   }
}

Sample Code:

Web Service Method: ProcessXmlRequest (SOAP)

Request Format: XML over SOAP, Protocols: HTTP POST, HTTPS POST, Response Formats: XML, JSON*
Example Server Path: https://customname.datatoolscloud.net.au/KleberWebServiceSoap/DtKleberService.svc
SOAP WSDL: https://customname.datatoolscloud.net.au/KleberWebServiceSoap/DtKleberService.svc?wsdl

Sample XML Request:
<DtRequest Method="DataTools.Capture.Address.Predictive.CaPaf.SearchAddress" AddressLine="" ResultLimit="" ReturnGroupResults="" PreviousSearchRecordId="" RequestId="" RequestKey="" DepartmentCode="" />

Sample XML Response:
<DtResponse RequestId="" ResultCount="1" ErrorMessage="">
  <Result RecordId="" AddressLine="" NextSearch="" />
</DtResponse>

SOAP Envelope: The XML request is passed through a single parameter in the SOAP envelope <DtXmlRequest>. Where the development language requires the SOAP envelope contents to be defined manually, the additional step of encoding the Dt XML Request is required. The encoding required needs to transform "<" of the DtRequest to "<" and ">" to ">". See example below.

Sample SOAP Envelope:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/">
  <soapenv:Header/>
  <soapenv:Body>
    <tem:ProcessXmlRequest>
      <!--Optional:-->
      <tem:DtXmlRequest>
        &lt;DtRequest Method="DataTools.Capture.Address.Predictive.CaPaf.SearchAddress" AddressLine="" ResultLimit="" ReturnGroupResults="" PreviousSearchRecordId="" RequestId="" RequestKey="" DepartmentCode="" /&gt;
      </tem:DtXmlRequest>
    </tem:ProcessXmlRequest>
  </soapenv:Body>
</soapenv:Envelope>

Batching Requests: Use the <DtRequests> (plural) tag to send through multiple requests in a single transaction.

<DtRequests>
    <DtRequest Method="DataTools.Capture.Address.Predictive.CaPaf.SearchAddress" AddressLine="" ResultLimit="" ReturnGroupResults="" PreviousSearchRecordId="" RequestId="" RequestKey="" DepartmentCode="" />
    <DtRequest Method="DataTools.Capture.Address.Predictive.CaPaf.SearchAddress" AddressLine="" ResultLimit="" ReturnGroupResults="" PreviousSearchRecordId="" RequestId="" RequestKey="" DepartmentCode="" />
</DtRequests>

Sample Code:

* Add the additional input parameter "OutputFormat=json" or "OutputFormat=xml" to change the response format from default.
* Add the additional input parameter "callback" to convert JSON responses to JSONP responses for across domains support.
CORS header included where callback is not defined.

Please Note:
Ensure you thoroughly test all the methods you are using and are happy with the results before going into production. DataTools is charged by the data suppliers for use of every method – therefore ALL calls to any method will incur a COST. When you register DataTools provides you with free credit to help with development and trialling of the service. Once that credit is used you will need to purchase a monthly subscription and/or top up to continue using the service, even for development purposes. Please check the Method Pricing List for all current costs. DataTools does not warrant or guarantee the quality of the results returned and will not be held responsible for any costs incurred by using a method. Should you have any questions please contact your Sales representative or the Client Services team.