Skip to content
  • Documentation

    Loqate basics

    Code illustration

    Start here

    Enrich your address data with our combined solution

    Documentation

    • Address Capture

      Capture global addresses in real time using type-ahead address lookups

    • Address Verify

      Verify, correct and enrich address data with precision & confidence, globally and at scale

    • Store Finder
    • Email Validation
    • Phone Validation
    • Bank Validation
    • Geocode

    Integrations

    • Adobe Commerce (Magento)
    • BigCommerce
    • commercetools
    • Microsoft Dynamics 365
    • Shopify Plus
    • Shopware 6

    Support

    • FAQs
    • Support by product
    • Current service status
    • GB - English
    • US - English
    • DE - Deutsch
    • ANZ - English
    • IT - Italiano
    • ES - Español
    • NL - Nederlands
    • CN - 中文
Log in Get a demo
  • Loqate Basics
    • Start Here
    • Ways To Integrate
    • Creating API Keys
    • List Of Endpoints
    • API Security
    • Monitoring Account Usage
  • Product support
    • Address Capture
    • Address Verify
    • Store Finder
    • Email Validation
    • Phone Validation
    • Bank Validation
    • Geocode
    • Matchcode (legacy)
  • Guides
    • Address, Email and Phone Validation
      • Quick setup guide – Address, Email and Phone Validation
      • Advanced Setup Guide
      • Address Capture Integration Best Practice
      • Enabling new Capture features
      • SaaS Platform: Setting up a new service
      • SaaS Platform: Integration options
      • SaaS Platform: SDK
      • The Loqate Saas Platform
    • Data Maintenance
      • Data Maintenance - Post Processing
    • Data Sets
      • Consuming Premium Data Sets
      • Property Intelligence User Guide
      • Property Intelligence Data Directory
    • Integrations by platform
      • Adobe Commerce (Magento)
      • BigCommerce
      • commercetools
      • Microsoft Dynamics 365
      • Shopify Plus
      • Shopware 6
    • Store Finder
      • How Does a Store Finder Work?
      • Creating and Managing Location Lists
      • How To Implement a Store Finder
      • Setting Up Store Finder Keys
    • Utilities Register
      • Loqate Utilities Register 2.0
  • APIs
    • Address Capture
    • Address Verify
    • Store Finder
    • Email Validation
    • Phone Validation
    • Bank Validation
    • Geocode
    • Generic Errors
  • Sandbox
  • FAQs
    • Address Capture
    • Address Verification
    • Bank Account Verification
    • Common account errors
    • Data Maintenance Annual Subscription
    • Email Verification
    • General
    • Geocoding
    • Geolocation
    • Phone Verification
    • Technical

AddressBase Premium Integration Guide


AddressBase Premium from Ordnance Survey is a Premium source of detailed address intelligence for both business and government.

It is built through a combination the Ordnance Survey’s own research, the LLPG (Council Data) and PAF (Postal Address File).

It includes:

  • 40m records
  • Unique Property Reference Number (UPRN) - which remains constant for the entire lifecycle of all buidlings in the UK
  • Alternative, Historic and Provisional address versions for all buildings (linked via UPRN)
  • 1m accurate geocode
  • Lifecycle – Date entered and Last update

About This Guide

This guide explains how to access GBGroup's web service products using their Identity Management Platform (IdM), available via SOAP web services. The document provides a general description of the available functionality along with a definition of the corresponding interfaces used to access different datasets and services.

The fundamentals of integrating with the service are described here: Integration Fundamentals 

Section 2 of the document gives product specific details regarding the use of the Matchcode AddressBase Premium Web Service products via IdM.

The Matchcode AddressBase Premium service provides access to the AddressBase Premium data, in a similar manner to Matchcode UK Address searching (see Matchcode UK Address Integration Guide)

The Matchcode AddressBase Premium web service products are available via the Identity Management ExecuteCapture web service method.

Please note: Wherever <LatestWSDLVersion> is shown in Example Code below, please replace this with GlobalServices21a.wsdl.

Matchcode Names Web Service Product Information

The Matchcode Names service provides access to UK names information in a similar manner to Matchcode UK Address searching (see Matchcode UK Address Integration Guide)

The Matchcode Names web service products are available via the Identity Management ExecuteCapture web service method.

Input Format

The ExecuteCapture method takes in a ExecuteCaptureRequest data structure, which contains all the information necessary to carry out the request.

Type: ExecuteCaptureRequest

Field Name Type Description
securityHeader SecurityHeader The username and authentication token used to access the system.
profileRequest ProfileRequestCapture Details of the request


The SecurityHeader structure holds security data to access products and services in the IdM Platform.

The ProfileRequestCapture structure contains the criteria to identify the target product being called and the search data for the product request.

Within the profileRequest element, the profileGuid element should contain the GUID value listed below:

Profile GUID
AddressBase Premium BCB96C1A-BC4C-4110-8A9E-A097B55380BB

Search Criteria

The address search criteria should be entered into the IdmDataSearchAddress data structure, which is located within the input details as follows:

ExecuteCapture → ProfileRequestCapture → ProfileRequestCaptureData → address

Alternative Search Criteria

Along with the standard address search criteria, this service supports address searching by one of the address identifiers listed below.

This search criteria is specified by using the additionalItems property of the search address. To carry out a search with one of these identifiers, a key-value pair must be included in the additional items property, with the key being the identifier and the value being the search value. Only one identifier can be used in a search, if more than one are specified the others will be ignored.

This alternative search criteria overrides the standard address search criteria, which will be ignored if a valid identifier is provided in the IDM request.

Key Description
UPRN Unique property reference number
USRN Unique Street Reference Number
RM_UDPRN Royal Mail unique delivery point reference number
PARENT_UPRN Parent Unique property reference number
LPI_KEY LPI Key
XREFMA XREFMA Address Layer 2 TOID
XREFMT XREFMT Topography Layer TOID
XREFMI XREFMI Transport Network TOID
XREFVC XREFVC Council Tax
XREFVN XREFVN Non-Domestic Rates

Additional Request Options

The additional search options, used for configuring options such as casing or transliteration of output results, can be set in the IdmRequestOptions structure located in the ProfileRequestCaptureData.options property.

Additional Return Data

Additional data can be returned, or excluded from being returned, for each address by providing one or more values in the IdmRequestOption.relatedDataItems property.

Note: For each value provided, the corresponding data is returned, and the corresponding additional data for all the values not provided are not returned. So, for example, if OSLAUA is specified as a relatedDataItem, then the country code, udprn, geocode data (easting, northing, latitude, longitude) and person data (title, first, middle, last names, gender, date-of-birth) will no longer be returned by default; those fields must then be explicitly also requested as relatedDataitems.

The following values are supported by this service. 

Key Mnemonic Description Returned By Default
COUNTRYCODE Country code Yes
UPRN Unique property reference number Yes
XREFMI XREFMI Transport Network TOID Yes
XREFMA XREFMA Address Layer 2 TOID Yes
XREFMT XREFMT Topography Layer TOID Yes
XREFVC XREFVC Council Tax Yes
XREFVN XREFVN Non-Domestic Rates Yes
RM_UDPRN Royal Mail Unique Delivery Point Reference Number Yes
BLPU_STATUS BLPU Logical Status Yes
BLPU_STATE BLPU State Yes
BLPU_STATE_DATE BLPU State Date Yes
PARENT_UPRN Parent UPRN Yes
X_COORDINATE Easting Yes
Y_COORDINATE Northing Yes
RPC Representative Point Code Yes
BLPU_CUSTODIAN LLPG Custodian Yes
BLPU_START_DATE BLPU Start Date Yes
BLPU_END_DATE BLPU End Date Yes
BLPU_UPDATE_DATE BLPU Update Date Yes
BLPU_ENTRY_DATE BLPU Entry Date Yes
POSTAL_ADDRESS Postal Address Yes
MULTI_OCC_COUNT Multi-Occupancy Count Yes
CLASS_KEY Class Key Yes
CLASS_CODE Class Code Yes
CLASS_SCHEME Scheme Yes
CLASS_START_DATE Class Start Date Yes
CLASS_END_DATE Class End Date Yes
CLASS_UPDATE_DATE Class Update Date Yes
CLASS_ENTRY_DATE Class Entry Date Yes
CLASS_PRIMARY Class Primary No
CLASS_SECONDARY Class Secondary No
CLASS_TERTIARY Class Tertiary No
CLASS_QUATERNARY Class Quaternary No
LPI_KEY LPI Key Yes
LANGUAGE Language Yes
LPI_STATUS LPI Logical Status Yes
LPI_START_DATE LPI Start Date Yes
LPI_END_DATE LPI End Date Yes
LPI_UPDATE_DATE LPI Update Date Yes
LPI_ENTRY_DATE LPI Entry Date Yes
SAO_START_NUMBER SAO Start Number Yes
SAO_START_SUFFIX SAO Start Suffix Yes
SAO_END_NUMBER SAO End Number Yes
SAO_END_SUFFIX SAO End Suffix Yes
SAO_TEXT SAO Text Yes
PAO_START_NUMBER PAO Start Number Yes
PAO_START_SUFFIX PAO Start Suffix Yes
PAO_END_NUMBER PAO End Number Yes
PAO_END_SUFFIX PAO End Suffix Yes
PAO_TEXT PAO Text Yes
USRN Unique Street Reference Number Yes
USRN_MATCH_INDI USRN Match Indicator Yes
AREA_NAME Area Name Yes
LEVEL Memorandum of Vertical Position Yes
OFFICIAL_FLAG Status of the Address Yes
ST_DESCRIPTION Street Name Yes
ST_LOCALITY Street Locality Name Yes
ST_TOWN Street Town Name Yes
ST_ADMIN_AREA Highway Authority Name Yes
ST_LANGUAGE Street Descriptor Language Yes
ST_TYPE Street Type Yes
ST_NAMING_AUTH Street Naming Authority Yes
ST_STATE Street State Yes
ST_STATE_DATE Street State Date Yes
ST_SURFACE Street Surface Finish Yes
ST_CLASS Street Class Yes
ST_VERSION Street Version Yes
ST_UPDATE_DATE Street Update Date Yes
ST_ENTRY_DATE Street Entry Date Yes
ST_START_DATE Street Start Date Yes
ST_END_DATE Street End Date Yes
ST_START_X Street Start X (Easting) Yes
ST_START_Y Street Start Y (Northing) Yes
ST_END_X Street End X (Easting) Yes
ST_END_Y Street End Y (Northing) Yes
ST_TOLERANCE Street Tolerance Yes
ORG_ORGANISATION Organisation Name Yes
ORG_LEGAL_NAME Organisation Registered Legal Name Yes
ORG_START_DATE Organisation Start Date Yes
ORG_END_DATE Organisation End Date Yes
ORG_UPDATE_DATE Organisation Update Date Yes
ORG_ENTRY_DATE Organisation Entry Date Yes

Request Additional Datasets

Data from additional datasets can be enabled or disabled for an address search, by populating the ProfileRequestCaptureData.additionalData property with key-value pairs from the applicable list table below. To use a particular dataset, the user must be subscribed to the dataset.

This information should be entered into the IdmDataArrayAdditionalData data structure, which is located within the input details as follows:

ExecuteCapture → ProfileRequestCapture → ProfileRequestCaptureData → additionalData

Key Possible Values Description
LOC_INT "Yes" or "No" Request Location Intelligence information to be returned
PREMISE_GEOCODE "Yes" or "No" Request Premise Level Geocode information to be returned

Location Intelligence

The Location Intelligence dataset is detailed here.

Premise Level Geocodes

The Premise Level Geocodes dataset is detailed here.

Address Filters

Addresses which have been found by the web service, which match a particular kind of address, can be filtered out from the search results by using the address filters functionality described here.

Output Format

The results of the Matchcode Names web service search are returned in a ProfileResponseDetails structure with a ProfileResponseDetail.responseType of 'CAPTURE'.

The ProfileResponseDetails structure contains a single CaptureResponse data structure which holds an array of IdmDataAddress records containing the returned address data.

ExecuteCaptureResponse > ProfileResponse [0] > ProfileResponseDetails [0] > CaptureResponse > CaptureResponseData > IdmDataAddress [n]

Additional data from a search may be returned in the additionalItems or the groupedAdditionalItems of the IdmDataAddress.

Output Fields

Apart from the standard address fields, the following additional fields are returned by the service:

Field Related Data Item Key Location In Response
BLPU_STATUS BLPU_STATUS IdmDataAddress → IdmDataBLPU → blpuLogicalStatus
BLPU_STATE BLPU_STATE IdmDataAddress → IdmDataBLPU → blpuState
BLPU_STATE_DATE BLPU_STATE_DATE IdmDataAddress → IdmDataBLPU → blpuStateDate
PARENT_UPRN PARENT_UPRN IdmDataAddress → IdmDataBLPU → parentUprn
X_COORDINATE X_COORDINATE IdmDataAddress → IdmDataBLPU → easting
Y_COORDINATE Y_COORDINATE IdmDataAddress → IdmDataBLPU → northing
RPC RPC IdmDataAddress → IdmDataBLPU → rpc
BLPU_CUSTODIAN BLPU_CUSTODIAN IdmDataAddress → IdmDataBLPU → localCustodianCode
BLPU_START_DATE BLPU_START_DATE IdmDataAddress → IdmDataBLPU → blpuStartDate
BLPU_END_DATE BLPU_END_DATE IdmDataAddress → IdmDataBLPU → blpuEndDate
BLPU_UPDATE_DATE BLPU_UPDATE_DATE IdmDataAddress → IdmDataBLPU → blpuLastUpdateDate
BLPU_ENTRY_DATE BLPU_ENTRY_DATE IdmDataAddress → IdmDataBLPU → blpuEntryDate
POSTAL_ADDRESS POSTAL_ADDRESS IdmDataAddress → IdmDataBLPU → postalAddressable
POSTCODE_LOCATOR N/A IdmDataAddress → IdmDataBLPU → postcodeLocator
MULTI_OCC_COUNT MULTI_OCC_COUNT IdmDataAddress → IdmDataBLPU → multiOccCount
CLASS_KEY CLASS_KEY IdmDataAddress → IdmDataClassification → classKey
CLASS_CODE CLASS_CODE IdmDataAddress → IdmDataClassification → classificationCode
CLASS_SCHEME CLASS_SCHEME IdmDataAddress → IdmDataClassification → classScheme
CLASS_START_DATE CLASS_START_DATE IdmDataAddress → IdmDataClassification → classStartDate
CLASS_END_DATE CLASS_END_DATE IdmDataAddress  → IdmDataClassification  → classEndDate
CLASS_UPDATE_DATE CLASS_UPDATE_DATE IdmDataAddress → IdmDataClassification → classLastUpdateDate
CLASS_ENTRY_DATE CLASS_ENTRY_DATE IdmDataAddress → IdmDataClassification → entryDate
CLASS_PRIMARY CLASS_PRIMARY IdmDataAddress → IdmDataClassification → classPrimaryText
CLASS_SECONDARY CLASS_SECONDARY IdmDataAddress → IdmDataClassification → classSecondaryText
CLASS_TERTIARY CLASS_TERTIARY IdmDataAddress → IdmDataClassification → classTertiaryText
CLASS_QUATERNARY CLASS_QUATERNARY IdmDataAddress → IdmDataClassification → classQuaternaryText
LPI_KEY LPI_KEY IdmDataAddress → IdmDataLPI → lpiKey
LANGUAGE LANGUAGE IdmDataAddress → IdmDataLPI → lpiLanguage
LPI_STATUS LPI_STATUS IdmDataAddress → IdmDataLPI → lpiLogicalStatus
LPI_START_DATE LPI_START_DATE IdmDataAddress → IdmDataLPI → lpiStartDate
LPI_END_DATE LPI_END_DATE IdmDataAddress → IdmDataLPI → lpiEndDate
LPI_UPDATE_DATE LPI_UPDATE_DATE IdmDataAddress → IdmDataLPI → lpiLastUpdateDate
LPI_ENTRY_DATE LPI_ENTRY_DATE IdmDataAddress → IdmDataLPI → lpiEntryDate
SAO_START_NUMBER SAO_START_NUMBER IdmDataAddress → IdmDataLPI → saoStartNumber
SAO_START_SUFFIX SAO_START_SUFFIX IdmDataAddress → IdmDataLPI → saoStartSuffix
SAO_END_NUMBER SAO_END_NUMBER IdmDataAddress → IdmDataLPI → saoEndNumber
SAO_END_SUFFIX SAO_END_SUFFIX IdmDataAddress → IdmDataLPI → saoEndSuffix
SAO_TEXT SAO_TEXT IdmDataAddress → IdmDataLPI → saoText
PAO_START_NUMBER PAO_START_NUMBER IdmDataAddress → IdmDataLPI → paoStartNumber
PAO_START_SUFFIX PAO_START_SUFFIX IdmDataAddress → IdmDataLPI → paoStartSuffix
PAO_END_NUMBER PAO_END_NUMBER IdmDataAddress → IdmDataLPI → paoEndNumber
PAO_END_SUFFIX PAO_END_SUFFIX IdmDataAddress → IdmDataLPI → paoEndSuffix
PAO_TEXT PAO_TEXT IdmDataAddress → IdmDataLPI → paoText
USRN USRN IdmDataAddress → IdmDataLPI → usrn
USRN_MATCH_INDI USRN_MATCH_INDI IdmDataAddress → IdmDataLPI → usrnMatchIndicator
AREA_NAME AREA_NAME IdmDataAddress → IdmDataLPI → areaName
LEVEL LEVEL IdmDataAddress → IdmDataLPI → level
OFFICIAL_FLAG OFFICIAL_FLAG IdmDataAddress → IdmDataLPI → officialFlag
ST_DESCRIPTION ST_DESCRIPTION IdmDataAddress → IdmDataStreetDescriptor → streetDescription
ST_LOCALITY ST_LOCALITY IdmDataAddress → IdmDataStreetDescriptor → locality
ST_TOWN ST_TOWN IdmDataAddress → IdmDataStreetDescriptor → townName
ST_ADMIN_AREA ST_ADMIN_AREA IdmDataAddress → IdmDataStreetDescriptor  → administrativeArea
ST_LANGUAGE ST_LANGUAGE IdmDataAddress → IdmDataStreetDescriptor → streetLanguage
ST_TYPE ST_TYPE IdmDataAddress → IdmDataStreetInformation → streetType
ST_NAMING_AUTH ST_NAMING_AUTH IdmDataAddress → IdmDataStreetInformation → swaOrgRefNaming
ST_STATE ST_STATE IdmDataAddress → IdmDataStreetInformation → streetState
ST_STATE_DATE ST_STATE_DATE IdmDataAddress → IdmDataStreetInformation → stateDate
ST_SURFACE ST_SURFACE IdmDataAddress → IdmDataStreetInformation → streetSurface
ST_CLASS ST_CLASS IdmDataAddress → IdmDataStreetInformation → streetClassification
ST_VERSION ST_VERSION IdmDataAddress → IdmDataStreetInformation → streetVersion
ST_UPDATE_DATE ST_UPDATE_DATE IdmDataAddress → IdmDataStreetInformation → streetLastUpdateDate
ST_ENTRY_DATE ST_ENTRY_DATE IdmDataAddress → IdmDataStreetInformation → streetEntryDate
ST_START_DATE ST_START_DATE IdmDataAddress → IdmDataStreetInformation → streetStartDate
ST_END_DATE ST_END_DATE IdmDataAddress → IdmDataStreetInformation → streetEndDate
ST_START_X ST_START_X IdmDataAddress → IdmDataStreetInformation → streetStartEasting
ST_START_Y ST_START_Y IdmDataAddress → IdmDataStreetInformation → streetStartNorthing
ST_END_X ST_END_X IdmDataAddress → IdmDataStreetInformation → streetEndEasting
ST_END_Y ST_END_Y IdmDataAddress → IdmDataStreetInformation  → streetEndNorthing
ST_TOLERANCE ST_TOLERANCE IdmDataAddress → IdmDataStreetInformation → streetTolerance
ORG_ORGANISATION ORG_ORGANISATION IdmDataAddress → IdmDataCompanyInformation → organisationName
ORG_LEGAL_NAME ORG_LEGAL_NAME IdmDataAddress → IdmDataCompanyInformation → legalOrganisationLegalName
ORG_START_DATE ORG_START_DATE IdmDataAddress → IdmDataCompanyInformation → organisationStartDate
ORG_END_DATE ORG_END_DATE IdmDataAddress → IdmDataCompanyInformation → organisationEndDate
ORG_UPDATE_DATE ORG_UPDATE_DATE IdmDataAddress → IdmDataCompanyInformation → organisationLastUpdateDate
ORG_ENTRY_DATE ORG_ENTRY_DATE IdmDataAddress → IdmDataCompanyInformation → organisationEntryDate
UPRN UPRN IdmDataAddress → uprn
XREFMA XREFMA IdmDataAddress → osAl2Toid
XREFMI XREFMI IdmDataAddress → osItnToid
XREFMT XREFMT IdmDataAddress → osTopoToid
XREFVC XREFVC IdmDataAddress → voaCtRecord
XREFVN XREFVN IdmDataAddress → voaNdrRecord
RM_UDPRN RM_UDPRN IdmDataAddress → rmUDPRN

Example Requests & Responses


Example Requests

The following example shows how to use the alternative search criteria mentioned previously, to to search for an address by its LPI_KEY value.


SOAP
<soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
                  xmlns:a="http://gbworld.gb.co.uk/idm-globalservices/messages/<LatestWSDLVersion>/"
                  xmlns:head="http://gbworld.gb.co.uk/types/header/"
                  xmlns:req="http://gbworld.gb.co.uk/types/core/request/"
                  xmlns:data="http://gbworld.gb.co.uk/types/core/data/">
    <soapenv:header/>
    <soapenv:body>
        <a:executecapturerequest>
            <a:securityheader>
                <head:authenticationtoken>C18AB65D-85A0-4C48-81A9-C5E23058C819</head:authenticationtoken>
                <head:username>CENSORED</head:username>
            </a:securityheader>
            <a:profilerequest>
                <req:customerreference>Sample ABP Lookup</req:customerreference>
                <req:profileguid>BCB96C1A-BC4C-4110-8A9E-A097B55380BB</req:profileguid>
                <req:configurationid>1</req:configurationid>
                <req:requestdata>
                    <req:address>
                        <data:additionalItems>
                            <data:item>
                                <data:key>UPRN</data:key>
                                <data:value>5030L000003836</data:value>
                                <!-- "Bank Of England,Threadneedle Street,London,EC2R 8AH" -->
                            </data:item>
                        </data:additionalItems>
                    </req:address>
                    <req:filters tmp="?"/>
                    <req:options>
                        <req:addressenvelopeformat>A4P</req:addressenvelopeformat>
                        <req:offset>0</req:offset>
                        <req:maxreturn>50</req:maxreturn>
                        <req:transliteration>NATIVE</req:transliteration>
                        <req:countrycodeformat>ISO3</req:countrycodeformat>
                    </req:options>
                    <req:additionaldata tmp="?"/>
                </req:requestdata>
            </a:profilerequest>
        </a:executecapturerequest>
    </soapenv:body>
</soapenv:envelope>

Example Responses


SOAP
<soap-env:envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    <soap-env:header/>
    <soap-env:body>
        <ns5:executecaptureresponse xmlns:ns5="http://gbworld.gb.co.uk/idm-globalservices/messages/<LatestWSDLVersion>/"
                                    xmlns:data="http://gbworld.gb.co.uk/types/core/data/"
                                    xmlns:head="http://gbworld.gb.co.uk/types/header/"
                                    xmlns:req="http://gbworld.gb.co.uk/types/core/request/">
            <ns5:securityheader>
                <head:authenticationtoken>1273F4FA-3AE7-4742-A0C6-626D006A445A</head:authenticationtoken>
                <head:authenticationtime>2014-02-14T13:05:11.000Z</head:authenticationtime>
                <head:sessionexpirytime>2014-02-14T13:35:20.449Z</head:sessionexpirytime>
            </ns5:securityheader>
            <ns5:transactionguid>8F9F9258-E772-45FC-B486-7F09FD3F067B</ns5:transactionguid>
            <ns5:profileresponse>
                <req:profileheader>
                    <req:profileguid>BCB96C1A-BC4C-4110-8A9E-A097B55380BB</req:profileguid>
                    <req:profilename>Matchcode AddressBase</req:profilename>
                    <req:transactionguid>8F9F9258-E772-45FC-B486-7F09FD3F067B</req:transactionguid>
                    <req:transactiontimestamp>2014-02-14T13:05:20.537Z</req:transactiontimestamp>
                    <req:profilestatus>SUCCESS</req:profilestatus>
                </req:profileheader>
                <req:profileresponsedetails>
                    <req:transactionguid>87F581B6-5EC4-4F5D-9335-245B95C33B05</req:transactionguid>
                    <req:componentname>AddressBase</req:componentname>
                    <req:componentstatus>SUCCESS</req:componentstatus>
                    <req:componentaction>VERIFY</req:componentaction>
                    <req:responsetype>CAPTURE</req:responsetype>
                    <req:notes>[]</req:notes>
                    <req:invoice>
                        <req:invoicelist>
                            <req:invoiceguid>8BBC5551-5093-4563-B03A-867E6482B7E6</req:invoiceguid>
                            <req:billinginformationguid>CCB1C022-BF7C-4C71-B445-710110FA0FC7
                            </req:billinginformationguid>
                            <req:billingpoints>1</req:billingpoints>
                            <req:creditsused>1</req:creditsused>
                            <req:datasetinvoices>
                                <req:datasetcode>ABP</req:datasetcode>
                                <req:billingpoints>1</req:billingpoints>
                                <req:recordsreturned>1</req:recordsreturned>
                                <req:datalicenceguid>CCB1C022-BF7C-4C71-B445-710110FA0FC7</req:datalicenceguid>
                            </req:datasetinvoices>
                        </req:invoicelist>
                    </req:invoice>
                    <req:captureresponse>
                        <req:resultStatus>SINGLE</req:resultStatus>
                        <req:recordsReturned>1</req:recordsReturned>
                        <req:moreData>false</req:moreData>
                        <req:totalRecordCount>1</req:totalRecordCount>
                        <req:totalPages>1</req:totalPages>
                        <req:matchScore>0</req:matchScore>
                        <req:matchLevel>NA</req:matchLevel>
                        <req:outputStatus>NOTMATCHED</req:outputStatus>
                        <req:fieldStatus/>
                        <req:responseCount>1</req:responseCount>
                        <req:response>
                            <req:address>
                                <data:street>Threadneedle Street</data:street>
                                <data:town>LONDON</data:town>
                                <data:postCode>EC2R 8AH</data:postCode>
                                <data:buildingName>The Bank Of England</data:buildingName>
                                <data:stateRegion>London</data:stateRegion>
                                <data:countryCode>GBR</data:countryCode>
                                <data:dpsZipPlus>9ZG</data:dpsZipPlus>
                                <data:formattedAddress>The Bank Of England,Threadneedle Street,,LONDON,,EC2R 8AH</data:formattedAddress>
                                <data:additionalItems>
                                    <data:item>
                                        <data:key>DATASOURCE</data:key>
                                        <data:value>ABP</data:value>
                                    </data:item>
                                </data:additionalItems>
                                <data:uprn>200000069805</data:uprn>
                                <data:lpi>
                                    <data:lpiKey>5030L000003836</data:lpiKey>
                                    <data:lpiLanguage>ENG</data:lpiLanguage>
                                    <data:lpiLogicalStatus>1</data:lpiLogicalStatus>
                                    <data:lpiStartDate>
                                        <data:day>29</data:day>
                                        <data:month>2</data:month>
                                        <data:year>2008</data:year>
                                    </data:lpiStartDate>
                                    <data:lpiLastUpdateDate>
                                        <data:day>10</data:day>
                                        <data:month>2</data:month>
                                        <data:year>2016</data:year>
                                    </data:lpiLastUpdateDate>
                                    <data:lpiEntryDate>
                                        <data:day>13</data:day>
                                        <data:month>6</data:month>
                                        <data:year>2001</data:year>
                                    </data:lpiEntryDate>
                                    <data:paoText>THE BANK OF ENGLAND</data:paoText>
                                    <data:usrn>8100535</data:usrn>
                                    <data:usrnMatchIndicator>1</data:usrnMatchIndicator>
                                </data:lpi>
                                <data:blpu>
                                    <data:blpuLogicalStatus>1</data:blpuLogicalStatus>
                                    <data:easting>532726.0</data:easting>
                                    <data:northing>181205.0</data:northing>
                                    <data:rpc>2</data:rpc>
                                    <data:localCustodianCode>5030</data:localCustodianCode>
                                    <data:blpuStartDate>
                                        <data:day>29</data:day>
                                        <data:month>2</data:month>
                                        <data:year>2008</data:year>
                                    </data:blpuStartDate>
                                    <data:blpuLastUpdateDate>
                                        <data:day>10</data:day>
                                        <data:month>2</data:month>
                                        <data:year>2016</data:year>
                                    </data:blpuLastUpdateDate>
                                    <data:blpuEntryDate>
                                        <data:day>16</data:day>
                                        <data:month>3</data:month>
                                        <data:year>2001</data:year>
                                    </data:blpuEntryDate>
                                    <data:postalAddressable>D</data:postalAddressable>
                                    <data:postcodeLocator>EC2R 8AH</data:postcodeLocator>
                                    <data:multiOccCount>0</data:multiOccCount>
                                </data:blpu>
                                <data:streetDescriptor>
                                    <data:streetDescription>THREADNEEDLE STREET</data:streetDescription>
                                    <data:townName>LONDON</data:townName>
                                    <data:administrativeArea>CITY OF LONDON</data:administrativeArea>
                                    <data:streetLanguage>ENG</data:streetLanguage>
                                </data:streetDescriptor>
                                <data:streetInformation>
                                    <data:streetType>1</data:streetType>
                                    <data:swaOrgRefNaming>5030</data:swaOrgRefNaming>
                                    <data:streetState>2</data:streetState>
                                    <data:stateDate>
                                        <data:day>19</data:day>
                                        <data:month>3</data:month>
                                        <data:year>1998</data:year>
                                    </data:stateDate>
                                    <data:streetSurface>1</data:streetSurface>
                                    <data:streetClassification>8</data:streetClassification>
                                    <data:streetVersion>0</data:streetVersion>
                                    <data:streetLastUpdateDate>
                                        <data:day>10</data:day>
                                        <data:month>2</data:month>
                                        <data:year>2016</data:year>
                                    </data:streetLastUpdateDate>
                                    <data:streetEntryDate>
                                        <data:day>19</data:day>
                                        <data:month>3</data:month>
                                        <data:year>1998</data:year>
                                    </data:streetEntryDate>
                                    <data:streetStartDate>
                                        <data:day>29</data:day>
                                        <data:month>2</data:month>
                                        <data:year>2008</data:year>
                                    </data:streetStartDate>
                                    <data:streetStartEasting>532706.0</data:streetStartEasting>
                                    <data:streetStartNorthing>181118.0</data:streetStartNorthing>
                                    <data:streetEndEasting>533069.02</data:streetEndEasting>
                                    <data:streetEndNorthing>181240.32</data:streetEndNorthing>
                                    <data:streetTolerance>1</data:streetTolerance>
                                </data:streetInformation>
                                <data:companyInformation/>
                                <data:classification>
                                    <data:classKey>5030C000004791</data:classKey>
                                    <data:classificationCode>CO01</data:classificationCode>
                                    <data:classStartDate>
                                        <data:day>29</data:day>
                                        <data:month>2</data:month>
                                        <data:year>2008</data:year>
                                    </data:classStartDate>
                                    <data:classLastUpdateDate>
                                        <data:day>10</data:day>
                                        <data:month>2</data:month>
                                        <data:year>2016</data:year>
                                    </data:classLastUpdateDate>
                                    <data:entryDate>
                                        <data:day>16</data:day>
                                        <data:month>3</data:month>
                                        <data:year>2001</data:year>
                                    </data:entryDate>
                                </data:classification>
                                <data:osAl2Toid>osgb1000002190901083</data:osAl2Toid>
                                <data:osItnToid>osgb4000000030344682</data:osItnToid>
                                <data:osTopoToid>osgb1000005892183</data:osTopoToid>
                                <data:voaNdrRecord>20403052</data:voaNdrRecord>
                                <data:rmUDPRN>27599055</data:rmUDPRN>
                            </req:address>
                        </req:response>
                    </req:captureresponse>
                </req:profileresponsedetails>
            </ns5:profileresponse>
        </ns5:executecaptureresponse>
    </soap-env:body>
</soap-env:envelope><br><br>

Error Information

Information on possible error codes is given here: Error Code Information

Starting with Loqate is simple, fast, and free

  • No credit card required
  • Cancel any time
  • 24/7 support
Request a demo
  • Product
  • Capture Verify Maintenance Bank Phone Email Geocode Nearest Value Add Services Data Technology Roadmap Our customers
  • Use cases
  • Reach a global audience Reduce failed deliveries Onboard customers Improve data quality
  • Resources
  • Newsroom Blogs & videos eBooks & reports Webinars & events
  • Get started & pricing
  • Free trial Request a demo Pricing Account login
  • Partners
  • Partner overview Ecosystem
  • Developers
  • Product support FAQs Guides API Integrations and plugins Sandbox Service status
  • Get in touch
  • Customer support Contact us
  • Company
  • About us GBG website Investors GBG Trust Centre
  • Legal
  • Privacy policy Products & services privacy policy Privacy approach Cookie policy Cookie preferences Accessibility policy

We are the world's most trusted specialist for location data. Our innovative technology gives customers the ability to verify addresses at the point of capture, with a simple, and easy to integrate address validation API.

© 2025 GB Group plc ('GBG'). GBG is the trading name and a trademark of GB Group plc.

G2 Users Love Us G2 High Performer G2 Best Support G2 Fastest Implementation