AddressVal™ is available on both main and backup servers at our primary and secondary data centres.
In general:
1 AddressVal™ - REST
where:
If the postcode is valid:-
Sample valid response in xml format :-
<addresses>
<address>
</address>
<address>
</address>
</addresses>
Sample valid response in json format :-
Sample valid response in csv format :-
If premise and postcode are not valid or if an error occurs:-
Error messages :-
ERROR - UserID Expired - Trial user ID has expired.
ERROR - Invalid User ID/PIN - The User ID or PIN has not been recognised.
ERROR - Insufficient address input - The postcode is not complete.
ERROR - No matching address found - The postcode is not valid.
ERROR - Too many matching addresses - Too many matching addresses for given input.
2 AddressVal™ - SOAP
The simplest way to access the SOAP service is via its WSDL (Web Service Definition Language) file. This can be used by many SOAP toolkits to generate the client code necessary to consume the web service.
ReturnMessage = addresscheck(QueryString)
where
QueryString is a " | " delimited string of the format - "userid|PIN|premise_name_or_number|postcode"
ReturnMessage is string delimited by coma and pipe characters or an error message as shown below.
Example Valid Results
A typical example of an exact match might look like:-
A example of a ‘fuzzy’ match might look like:-
If premise and postcode are not valid or if an error occurs:-
Error Message
ERROR - UserID Expired - Trial user ID has expired.
ERROR - Invalid User ID/PIN - The User ID or PIN has not been recognised.
ERROR - Insufficient address input - The postcode is not complete.
ERROR - No matching address found - The postcode is not valid.
ERROR - Too many matching addresses - Too many matching addresses for given input.
Social Media