Matchcode UK Powersearch Integration Guide
UK Powersearch, also known as single-line auto-complete, is a "Google-like" search method by which the user types into a single text field and is shown a list of potential matches which is rebuilt as they continue to type. This Service has been implemented as a REST Web Service in order to make a light Service achieving fast response times, allowing for an interactive user experience
UK Powersearch Searching
UK Powersearch will return a list of addresses matching to the information provided in the Request. This service need one input: The ADDRESS (or part of the address) to be found. The more accurate the information provided, the smaller the returned list. The way ADDRESS must be provided to the service will be detailed below.
Output Formatting Options
UK Powersearch provides the possibility to format the returning address. The formatting will only apply when the Response has just one address rather than a list of addresses. In case of list of addresses, the formatting will be skipped. The formatting options can be found here:
The way these formatting options must be supplied to the service will be detailed below.
Using the Powersearch REST Service
The UK Powersearch REST WebService offers its operation through the HTTP GET method so that all the data supplied to the Service must be in the URL as HTTP parameters.
The REST WebService offers the possibility to get the Response in two different formats: XML or JSON. In order to specify the preferred format in the Response the Accept Header Request Parameter must be supplied:
To get the Response in XML format: Accept: application/xml
To get the Response in JSon format: Accept: application/json
If the Accept Header Request Parameter is omitted, the XML format in the Response will be applied as the default format.
Authentication
As a REST Web Service, UK Powersearch uses Http Basic Authentication.
Briefly, the client must send its credentials (UserID and Password). This credentials must be the result of Base64 encoding of the next string: userID:password. This Base64 encoded string must be supplied as a Header Request Parameter.
Example:
The client wants to send the credentials Username: userexample and Password: passwordexample, so the string to send should be:
Authorization: Basic dXNlcmV4YW1wbGU6cGFzc3dvcmRleGFtcGxl
Authorization is the Header Request Parameter name, and Basic dXNlcmV4YW1wbGU6cGFzc3dvcmRleGFtcGxl the Header Request Parameter value where dXNlcmV4YW1wbGU6cGFzc3dvcmRleGFtcGxl is userexample:passwordexample encoded in Base64.
The above information must be sent within every request to the REST Web Service, so the client must be authenticated in every single request.
UK Address Data
These are several examples of UK Address Data Requests and Responses:
| Scenario | Notes |
|---|---|
| Address Search (not very accurate request) REQUEST | Enter the address to be found in the Request Parameter address
https://idmp.gb.co.uk/idm-powersearch-rest/powersearch/names?address=8 london road
|
| Address Search (not very accurate request) RESPONSE | As the Address introduced in the Request was not very accurate, the service return a list of matches. |
| Scenario | Notes |
|---|---|
| Address Search (accurate address) REQUEST | Enter the address to be found in the Request Parameter address
https://idmp.gb.co.uk/idm-powersearch-rest/powersearch/names?address=8 London Road, BALDOCK, Herts, SG7 6JN
|
| Address Search (accurate address) RESPONSE | As the Address introduced is very accurate, only one match is returned. |
| Scenario | Notes |
|---|---|
| Address Search (accurate address) & Formatting REQUEST | Enter the formatting option by using the Request Parameter format Parameter address
https://idmp.gb.co.uk/idm-powersearch-rest/powersearch/names?address=8 London Road, BALDOCK, Herts, SG7 6JN&format=LC=3
|
| Address Search (accurate address) & Formatting RESPONSE | According the formatting option introduced, the number of address lines must be 3 |
Session Management - IMPORTANT
UK Powersearch Address Searching provides a mechanism to ensure that the desired final address can be found within a fair time and number of transactions. Thus, all the requests needed to find an Address will be included in a Session. Sessions have a limit of either 50 transactions or 2 minutes.
If the client supplies a valid SessionKey, the request will be included in that Session. If the client supplies an invalid SessionKey or no SessionKey is provided (first request), the Powersearch Service will create a new Session where the current transaction will be included.
Note that an invalid SessionKey might be a wrong key or a key that represents a Session with more than 50 calls or more than 2 minutes of life.
Each new session key will result in a billing point and will therefore remove a credit for customers with Pre-pay transaction accounts. Please therefore ensure that Session keys are recycled throughout each instance of a customer searching for their address.
As it can be seen in the above examples, a SessionData element is returned in every UK Searching Response from the Service. This SessionData contains a SessionKey (to be used in next request), sessionCommencement (session commencement timestamp), and numberOfSessionsTransactions (number of Transactions already used in this Session)
This is an example of how to add a SessionKey to the request:
| Scenario | Notes |
|---|---|
| Including SessionKey in the UK Address Search REQUEST | Enter the parameter sessionkey with the SessionKey (got from the last Response to the Service).
https://idmp.gb.co.uk/idm-powersearch-rest/powersearch/names?address=york road f&sessionkey=2432D120-1F36-4894-861D-E319C7636A22
|
| UK Address Search RESPONSE | Address Search Response |