AV3 – Operations

List of Operations

• AV3 – GetBestMatches (Recommended Operation)
  • Returns parsed and validated address elements, and make corrections where possible. Multiple address candidates may be returned if a definitive decision cannot be made by the service.

• AV3 – GetSecondaryNumbers
  • Returns parsed and validated address elements along with a list of potential secondary numbers for a given input address.

• AV3 – FindAddressLines
  • Organizes bad address data by sorting up to six possible address lines and return what it thinks are the most probable candidates for Address1 and Address2.

• AV3 – ValidateAddressWithDPV
  • Returns parsed and validated address elements including Delivery Point Validation.

• AV3 – ValidateAddressWithRDI
  • Functions identically to ValidateAddressWithDPV except it also returns the “Residential Delivery Indicator” (RDI) flag.

• AV3 – ValidateAddressWithSLK
  • Functions identically to ValidateAddressWithDPV except it accepts a business name to potentially append Suite data if it’s missing.

• AV3 – ParseAddress
  • Parses an address into its individual address elements. This is purely a parsing method and it does not validate, correct or verify an address.

• AV3 – ValidateCityStateZip
  • This operation will validate that a given city-state-zip validate together properly. The inputs can be marginally incorrect, and this operation will correct them.

• AV3 – GetBestMatchesSingleLine
  • Takes a single address line as input and returns the validated and parsed address candidates. This operation may return more than one address if a definitive decision cannot be made by the service.

• AV3 – GetPossibleMatches (Deprecated)
  • This operation is almost exactly like ValidateAddressWithFragments, but may return multiple address with fragments.

• AV3 – ValidateAddressSingleLine (Deprecated)
  • ValidateAddressSingleLine behaves almost exactly like ValidateAddressWithFragments, but takes all of its input as a single field

• AV3 – GetPossibleMatchesSingleLine (Deprecated)
  • Often, users have addresses as a single line of data, which may or may not be separated by commas, slashes, spaces, etc. For this reason, ValidateAddressSingleLine behaves almost exactly like ValidateAddressWithFragments, but takes all of its input as a single field.