DataTools Kleber Method Description

Method:
DataTools.Match.BusinessName.CreateKeys
Use to generate match keys used to fuzzy match business names.

Test:

Parameter	Value
MatchKeySet
BusinessName
Locality
RequestId
RequestKey
DepartmentCode

Input Parameters:

Parameter	Description
MatchKeySet	Name of Match Key Set. If left blank default match keys will be generated.
BusinessName	Business Name eg. Parramatta Shoes Pty Ltd
Locality	Locality Name eg. Parramatta
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
StandardBusinessNameKey	Standard Business Name Key
TightBusinessNameKey	Tight Business Name Key
LooseBusinessNameKey	Loose Business Name Key

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.Match.BusinessName.CreateKeys&MatchKeySet=&BusinessName=&Locality=&RequestId=&RequestKey=&DepartmentCode=

Sample JSON Response:
{
   "DtResponse":{
      "RequestId":"",
      "ResultCount":"1",
      "ErrorMessage":"",
      "Result":[
         {
            "StandardBusinessNameKey":"",
            "TightBusinessNameKey":"",
            "LooseBusinessNameKey":""
         }
      ]
   }
}

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.Match.BusinessName.CreateKeys" MatchKeySet="" BusinessName="" Locality="" RequestId="" RequestKey="" DepartmentCode="" />

Sample XML Response:
<DtResponse RequestId="" ResultCount="1" ErrorMessage="">
  <Result StandardBusinessNameKey="" TightBusinessNameKey="" LooseBusinessNameKey="" />
</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.Match.BusinessName.CreateKeys" MatchKeySet="" BusinessName="" Locality="" 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.Match.BusinessName.CreateKeys" MatchKeySet="" BusinessName="" Locality="" RequestId="" RequestKey="" DepartmentCode="" />
    <DtRequest Method="DataTools.Match.BusinessName.CreateKeys" MatchKeySet="" BusinessName="" Locality="" 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.