...
The search algorithm is based on string matching, but with preference given to the postcode substring. For best results, the full postcode should always be used where possible and known, in combination with another unique element of the address string. As per the examples below
Search string | Data returned in JSON | ||
|---|---|---|---|
215 NW1 6XE |
| ||
Flat 10 NW1 6XE |
| ||
Bay Oil NW1 6XE |
|
NOTE: In the above examples, spaces are not necessary in the postcode, and searches with NW16XE will also work. Results can become a bit more spurious with other spacing. For example whilst "215 NW1 6XE" identifies the specific property, but "215 NW 16 XE" returns all properties in the postcode.
...
Where postcode is not known or is only partially known the search engine will aim to identify the best fit possible, as per the examples below.
Search String | Data returned in JSON | ||
|---|---|---|---|
219 Baker Street London |
| ||
Liberty Baker Street |
| ||
Liberty NW1 |
|
There is however no further "intelligence" in the search matching. For example if the search is done on Baker Road London (which does not exist), it would not consider Baker Street to be a better match, but would prefer addresses that included the word "Baker" and "Road" in the address string, as per the example below (which returns multiple other addresses).
Search String | Data returned in JSON | ||
|---|---|---|---|
215 Baker Road London |
|
Integration and IP Whitelisting
...