This operation organizes really bad address data that is broken up into multiple arbitrary address fields. This function will sort up to six possible address lines and return what it thinks are the most probable candidates for the USPS Address1 and possibly Address2. For example, people’s names in the Address1 line mixed with actual street address lines.

URL Endpoints

FindAddressLines Inputs

Name Type Description
Address1 String Address line of the address to validate. For example, “123 Main Street”.
Address2 String This line is for address information that does not contribute to DPV coding an address. For example “C/O John Smith” does not help validate the address, but is still useful in delivery.
Address3 String Additional address info that might belong in Address1 or Address2.
Address4 String Additional address info that might belong in Address1 or Address2.
Address5 String Additional address info that might belong in Address1 or Address2.
Address6 String Additional address info that might belong in Address1 or Address2.
City String The city to validate. E.g., “New York”. Required if Zip code is not provided.
State String The state (e.g., “NY”). Full names also accepted. Required if Zip not provided.
PostalCode String The zip code. Required if City and State not provided.
LicenseKey* String Your license key. Sign up for a free trial at serviceobjects.com/address-validation

FindAddressLines Outputs

AddressLinesResponse

Name Type Values Description
Address Address[] Varies The corrected address candidates.
Error Error Varies Error object indicating why the result was not returned. See Errors for more information.

Address

Name Type Values Description
BestAddress1 String Varies The most probable address line 1.
BestAddress2 String Varies The most probable address line 2.
City String Varies The city name.
State String Varies The state name.
Zip String Varies The zip code.