Checks if a postcode is syntactically valid, and returns the same postcode in a standard format suitable for printing as part of an address.
This method does not check whether an address actually exists at the postcode, only that the postcode is of the correct format.
If the postcode has a correct format, the IsValid part of the result is set to true and the Formatted part of the result is set to the same postcode in a standard format, e.g. "ch24ne" is converted to "CH2 4NE".
If the postcode does not have a correct format, the IsValid part of the result is set to false and the Formatted part of the result will not be specified.
This service is hosted in multiple countries. Select your preferred country to see the appropriate endpoint URLs.
| Protocol | URL |
|---|---|
| JSON |
JSON
https://webservices.data-8.co.uk/AddressCapture/ValidatePostcode.json |
| OPEN API |
OPEN API
https://webservices.data-8.co.uk/swagger/AddressCapture/swagger.json |
| SOAP |
SOAP
https://webservices.data-8.co.uk/addresscapture.asmx |
| MCP |
MCP
https://webservices.data-8.co.uk/mcp/addresscapture
validate_postcode) |
| Name | Description |
|---|---|
| username | username
See the available authentication methods. If you are using username & password authentication, specify the username to authenticate as. If you are using API Key authentication and you are not using the JSON, Javascript or ADO APIs, use your API Key here with the prefix |
| password | password
If you are using username & password authentication, specify the password to use for authentication. Otherwise leave this blank. |
| licence | licence
As the Royal Mail PAF database can be licensed in multiple ways, this parameter indicates under which license you are accessing the data. This must match the variant you have a license or credits for - if you are unsure which option to choose, please contact your account manager |
| postcode | postcode
The postcode to validate |
| options | options
An array of options that control further details of how this method operates. See the |
option parameter. Each option is specified as a key/value pair.
The list of available names is shown below, along with a description of the allowable values for that name.
| Name | Description |
|---|---|
| Common Options | |
| ApplicationName |
ApplicationName
Gives the name of the calling application - used to break down usage by application in the usage reports on the dashboard.
|
| Name | Description |
|---|---|
| Status | Status
Indicates whether the method call was successful, or if some error occurred. If the |
| IsValid | IsValid
Indicates if the postcode is syntactically valid or not. |
| Formatted | Formatted
If |
Requests to this method do not consume credits, but you must have some AddressCapture credits available.
Request Format
{
"licence": "WebClickFull",
"postcode": "ch24ne",
"options": {}
}
Response Format
{
"Status": {
"Success": true,
"CreditsRemaining": 1000
},
"IsValid": true,
"Formatted": "CH2 4NE"
}
Depending on your chosen authentication method you will need to modify this request slightly:
API Key
https://webservices.data-8.co.uk/AddressCapture/ValidatePostcode.json?key=your-api-keyand do NOT include the
username or password properties in the request JSON document.
Username and Password
https://webservices.data-8.co.uk/AddressCapture/ValidatePostcode.jsonand include
username and password properties in the request JSON document.Do not use for client-side requests!
JWT Token
https://webservices.data-8.co.uk/AddressCapture/ValidatePostcode.jsonInclude the JWT token in the request headers as:
Authorization: Bearer your-jwt-token| Parameter | Value |
|---|---|
| Parameters | |
| licence | licence
|
| postcode | postcode
|
| Common Options | |
| ApplicationName |
ApplicationName
|
Credits Remaining Today: 25 | |