Address Web Service Product Information
The UK Address web service products are available via the Identity Management ExecuteCapture web service method.Basic Name and Address Capture
Method: ExecuteCapture
The ExecuteCapture method is used to access the GBG Customer Registration products and services by invoking the corresponding profile.Input Details
Type: ExecuteCaptureRequest| Field Name | Type | Description |
|---|---|---|
| securityHeader | SecurityHeader | The username and authentication token used to access the system. |
| profileRequest | ProfileRequestCapture | Details of the request |
| Profile | GUID |
|---|---|
| ddress Premise | 6C49BC44-C104-41b2-BB62-2AE45A09DD54 |
| Address Street Level | C6356DD8-1CBA-4371-BE94-D5E08F1C777E |
Output Details
The ExecuteCaptureResponse structure contains the results of an capture query. The response contains the authentication token to be passed into subsequent web service calls. The latest authentication token should always be passed into service calls. Type: ExecuteCaptureResponse| Field Name | Type | Description |
|---|---|---|
| securityHeaderResponse | SecurityHeaderResponse | Authentication information for subsequent calls |
| transactionGuid | String | Unique transaction reference |
| profileResponse | ProfileResponse | Response to the query |
| Field Name | Type | Description |
|---|---|---|
| ProfileResponseHeader | ProfileResponseHeader | Contains the Profile information for the results of the query |
| profileResponses | ProfileResponseDetails | Response data to the query |
| Field Name | Type | Description |
|---|---|---|
| transactionGuid | String | Unique transaction identifier for the component e.g. Address Lookup component |
| componentName | String | Name of the component |
| componentStatus | Enum | SUCCESS, FAILURE, INSUFFICIENTCRITERIA, NA |
| componentAction | String | Component Action |
| responseType | Enum | CAPTURE |
| invoice | DataLicenceInvoice | List of charges for the query |
| captureResponse | CaptureResponse | Data from a component returning data e.g. Address lookup data |
| validateResponse | ValidateResponse | Data from a component returning validation responses e.g. Telephone Validation service |
| Field Name | Type | Description |
|---|---|---|
| resultStatus | Enum | NA, INSUFFICIENTCRITERIA, NONE, SINGLE, MULTIPLE, PICKLIST, VERIFY |
| recordsReturned | Int | Number individual of records returned e.g. number of addresses |
| moreData | Boolean | More data on the server |
| totalRecordCount | Int | Total records from the query |
| totalPages | Int | Pagination - Total pages |
| responseCount | Int | Number of groups of responses returned |
| response | CaptureResponseData | Response data |
| Field Name | Type | Description |
|---|---|---|
| resultStatus | Enum | NA, INSUFFICIENTCRITERIA, NONE, SINGLE, MULTIPLE, PICKLIST, VERIFY |
| recordsReturned | Int | Number individual of records returned e.g. number of addresses |
| responseCount | Int | Number of group of response returned |
| response | ValidateResponseData | Response data |
Sample XML
Sample request:Address Capture - 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 → IdmDataSearchAddressRadius Search Criteria
Address Web Service supports radius searching, where a match is made for premises within a specified radius of a given point. To trigger a radius search values must be provided in the IdmDataGeographic structure of the search address. The easting and northing values should be specified to 5-digit accuracy.Additional Search Criteria
Additional information can be searched upon by providing the key value pairs specified below to the IdmDataSearchAddress.additionalItems property. For example, if you require to search on Royal Mail Mailsort code the key ‘MSRN’ and the mailsort value should be provided. Below is a list of searchable related fields:| Key Mnemonic | Description |
|---|---|
| AKEY | 17 Digit Addresskey |
| AREA | Local Authority Area Code |
| EAST | Easting |
| MSRN | New Mailsort |
| MSRO | Old Mailsort |
| NHSC | DHA Code |
| NRTH | Northing |
| PABR | Postal Address Book Region |
| WARD | Local Authority Ward Code |
| Key Mnemonic | Description |
|---|---|
| BNAM | Building Name |
| DDLO | Double Dependant Locality |
| DEPT | Department |
| DPLO | Dependent Locality |
| DPTH | Dependent Thorofare |
Sample Search XML
Additional Execution Options
Configuration options for the GB Address Web Service search can be set in the IdmRequestOptions structure located in the ProfileRequestCaptureData.options property.| Extensible array of key value pairs for future additional conversation |
Additional Return Data
Additional data can be returned for each address by providing one of the following values to the IdmRequestOption.relatedDataItems property (See section 2.2.3 for an example):| Key Mnemonic | Description |
|---|---|
| AKEY | 17 Digit Addresskey |
| AREA | Local Authority Area Code |
| EAST | Easting |
| INCO | Incode Only |
| MSRN | New Mailsort |
| MSRO | Old Mailsort |
| NRTH | Northing |
| OUTC | Outcode Only |
| PABR | Postal Address Book Region |
| WARD | Local Authority Ward Code |
Envelope Format
Address web Service provides the option to return each address as it would appear on an envelope. The IdmRequestOptions.addressEnvelopeFormat property allows you to specify how this should data should be formatted. The following are valid configuration options:| Format Code | Description |
|---|---|
| A4P | Four address lines and postcode |
| A5P | Five address lines and postcode |
| A6P | Six address lines and postcode |
| A2TCP | Two address lines, town, county and postcode |
| A3TCP | Three address lines, town, county and postcode |
| A4TCP | Four address lines, town, county and postcode |
| NA4P | Name, four address lines and postcode |
| NA5P | Name, five address lines and postcode |
| NA6P | Name, six address lines and postcode |
| NA2TCP | Name, two address lines, town, county and postcode |
| NA3TCP | Name, three address lines, town, county and postcode |
| NA4TCP | Name, four address lines, town, county and postcode |
| A4P-B | Four address lines without business |
| A4TCP-B | Four address lines, town, county and postcode without business |
| PAF | All address elements |
Sample Options XML
Output Format
The results of the Matchcode UK Address 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]Sample Output XML
IdM to Royal Mail PAF
The IdM web services provide the address format in a generic international format. The GB Address Web Service product allows address searching capability on UK based addresses. The mapping between the generic international address structure of IdM web service and the Royal Mail Postal Address File (PAF) is detailed below: Data Mapping: IdmDataSearchAddress → Royal Mail PAF → IdmDataAddress| Input Field: IdmDataSearchAddress | PAF Field | PAF Field Code | Output Field: IdmDataAddress |
|---|---|---|---|
| organisation | Organisation | ORGN | organisation |
| department | Department | DEPT | department |
| subBuilding | Sub Building | SUBB | subBuilding |
| building* | Building Name | BNAM | buildingName |
| Building Number | BNUM | buildingNumber | |
| poBox | PO Box | POBX | poBox |
| street* | Thorofare | THOR | street |
| Dependent Thorofare | DPTH | subStreet | |
| locality* | Dependent Locality | DPLO | locality |
| Double Dependant Locality | DDLO | sublocality | |
| town | Post Town | TOWN | town |
| stateRegion | County | CNTY | stateRegion |
| countryCode | N/A | N/A | countryCode |
| postCode | Postal Code | PCOD | postCode |
- Composite fields - Composite input fields offer advanced searching capabilities by searching against multiple target fields. e.g.locality - Searches against PAF Dependant Locality, Double Dependant Locality and PostTown.

