Unify and manage your data

Address cleansing status fields

Learn about address cleansing status fields.

During address cleansing, the system returns both cleansed address fields and verification status fields when an address is verified.

If the address isn't verified, no address fields are returned. To return only verification status fields for unverified addresses, enable the returnUnverifiedStatus option. For details, see Address Cleansing Properties.

Some of the following status fields depend on the cleansing process or country-specific reference data.

These status fields indicate how each address component was processed during cleansing; whether it was verified, changed, added, or left unrecognized.

Table 1. Address Cleansing fields
FieldsDescription
AVC, VerificationStatus, and VerificationStatusDetails

For more information about these fields, see topic Understanding Address Verification Code.

DPVConfirmedIndicator, DPVFootnotes, and ResultsString
These fields are returned only when the CASS2 process is used.
Note:

For more information about these fields, see the CASS2 Field Descriptions page.

SerpStatusEx, Questionable, and Result These fields are returned only when the SERP process is used.
Note:

For more information about these fields, see the SERP Fields page.

Component-level field status indicators
AddressStatus, Address1Status, Address2Status, Address3Status, Address4Status, Address5Status, Address6Status, Address7Status, and Address8StatusShow the verification result for the Address or Address line fields. Values are returned only when returnUnverifiedStatus is set to true.
DeliveryAddressStatus, DeliveryAddress1Status to DeliveryAddress8StatusShow the verification result for DeliveryAddress fields. Includes per-line indicators when returned.
CountryStatusStatus code for the Country field after cleansing.
SuperAdministrativeAreaStatusStatus code for the super administrative area (e.g., regions above state level).
AdministrativeAreaStatusStatus of the state or province field after address cleansing.
SubAdministrativeAreaStatusStatus code for county- or district-level administrative areas.
LocalityStatusStatus of the locality field (e.g., city or municipality).
DependentLocalityStatusStatus code for dependent locality elements (e.g., neighborhoods).
DoubleDependentLocalityStatusStatus code for the smallest population areas, often nested within dependent localities.
ThoroughfareStatusStatus of the street or block address element.
DependentThoroughfareStatusStatus for any secondary thoroughfare component (e.g., a secondary street name).
PremiseStatusStatus of the premise number (e.g., house or building number).
BuildingStatusStatus code for the named building or business location.
SubBuildingStatusStatus for units within a building (e.g., apartment or suite).
SubBuildingFloorStatusStatus for the floor identifier in a sub-building, if parsed.
PostalCodeStatusStatus for the postal code or ZIP Code, including primary and secondary components.
OrganizationStatusStatus of the organization name at the address, if present.
PostBoxStatusStatus of the Post Box or PO Box component.

Each status field provides a Status that explains how the corresponding address component was handled during cleansing. Codes indicate whether the value was verified, corrected, added, identified from context, or left unrecognized.

CodeStatus NameDescription
0fsNotApplicableThe field is not applicable for returning a field status code.
1fsVerifiedNoChangeThe field has been verified using relevant reference data, and no changes were necessary.
2fsVerifiedAliasChangeThe field has been verified using relevant reference data, and an alias change has been made during parsing.
3fsVerifiedSmallChangeThe field has been verified using relevant reference data, and a minor spelling correction has been made.
4fsVerifiedLargeChangeThe field has been verified using relevant reference data, and a major spelling correction has been made.
5fsAddedThe field has been added based on relevant reference data.
6fsIdentifiedNoChangeThe field has been identified using relevant lexicon data, and no changes were necessary.
7fsIdentifiedAliasThe field has been identified using relevant lexicon data, and an alias change has been made.
8fsIdentifiedContextThe field has been identified using relevant context rules (not strictly reference or lexicon-driven).
9fsEmptyThe field is empty.
10fsUnrecognizedThe field is unrecognized—it could not be identified or verified using reference data, lexicon, or contextual rules.