Stay organized with collections Save and categorize content based on your preferences.
This document describes a number of real-world scenarios where the Address Validation API provides response signals that warrant an accept behavior from your system. See Example workflows in Build your validation logic for context.
Note: The examples here are illustrative, but don't cover all scenarios. Common example: acceptThis scenario illustrates an address in which your system would accept an address entered by a customer.
Address entered Region 76 Buckingham Palace Road, London SW1W 9TQ UK Verdict for an acceptable addressThe example below highlights the important signals.
{
"inputGranularity": "PREMISE",
"validationGranularity": "PREMISE",
"geocodeGranularity": "PREMISE",
"addressComplete": true
}
In addition to this, the response indicates the following:
hasUnconfirmedComponents remains falsehasInferredComponents remains falsehasReplacedComponents remains falsehasSpellCorrectedComponents remains falseWhen combined together, these signals indicate a high-quality address.
Action: Accept. Edge case examples: acceptThe following examples cover situations in which the verdict indicates address quality issues that warrant further investigation. These examples also illustrate how your logic can travel from the verdict to the address components to obtain a more complete picture in order to enhance your system logic.
This example illustrates entry of an Italian address with all address components present, along with no inferred or replaced components. However, the validationGranularity is ROUTE.
{
"inputGranularity": "SUB_PREMISE",
"validationGranularity": "ROUTE",
"geocodeGranularity": "ROUTE",
"addressComplete": true,
"hasUnconfirmedComponents": true
}
Further investigation of the address components reveals that the street number is UNCONFIRMED_BUT_PLAUSIBLE.
{
"text": "14",
"componentType": "street_number",
"confirmationLevel": "UNCONFIRMED_BUT_PLAUSIBLE"
}
This example illustrates entry of a US address with all address components present, with no inferred or replaced components. However, the validationGranularity is PREMISE_PROXIMITY.
{
"firstAddressLine": "975 CARSON DR",
"cityStateZipAddressLine": "SUNNYVALE CA 94086",
"city": "SUNNYVALE",
"state": "CA",
"zipCode": "94086"
"dpvConfirmation": "N",
"dpvFootnote": "AAM3",
"carrierRoute": "C031",
"carrierRouteIndicator": "D",
"postOfficeCity": "SUNNYVALE",
"postOfficeState": "CA",
"fipsCountyCode": "085",
"county": "SANTA CLARA",
}
dpvConfirmation code of N provides a strong signal to confirm the address with the customer or prompt them to fix it. The behavior you choose for this case ultimately depends on your required confidence level. See Implementation guidance in Build your validation logic for more details. Incomplete USPS data for a confirmed address
This example illustrates entry of a US address with all address components confirmed, with no inferred or replaced components, and a validationGranularity of PREMISE. However, the uspsData is not fully populated, and does not contain a dpvConfirmation value.
{
"inputGranularity": "PREMISE",
"validationGranularity": "PREMISE",
"geocodeGranularity": "PREMISE",
"addressComplete": true,
}
{
"standardizedAddress": {
"firstAddressLine": "155 VIA CONDADO WAY",
"cityStateZipAddressLine": "PALM BEACH GARDENS",
"city": "PALM BEACH GARDENS",
"state": "FL",
"zipCode": "33418"
},
"carrierRoute": "H018",
"postOfficeCity": "PALM BEACH GARDENS",
"postOfficeState": "FL"
}
validationGranularity of PREMISE gives a strong signal that this is a valid address. However, for a higher confidence level, you can prompt the customer to confirm the address. See Implementation guidance in Build your validation logic for more details. Note: The service receives updated USPS data periodically, so this example may no longer return incomplete USPS data. This example is meant to be illustrative rather than an accurate portrayal of the API response for this address.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-11 UTC."],[[["The Address Validation API provides signals to determine if an address should be accepted by your system, even with minor uncertainties."],["Addresses with `validationGranularity` of `PREMISE` and no unconfirmed/inferred/replaced components are generally safe to accept."],["Addresses with `UNCONFIRMED_BUT_PLAUSIBLE` street numbers can be accepted, but consider prompting the customer for confirmation for higher confidence."],["US addresses with `dpvConfirmation` of 'N' might require customer confirmation or correction, depending on your system's confidence requirements."],["Even with incomplete USPS data, addresses with `validationGranularity` of `PREMISE` can often be accepted, but consider prompting the customer for confirmation."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4