How do I validate addresses using the API?
How can I verify an address and create a shipment in one API call?
How granular is your address verification?
Why is this address not verifying?
I enabled address verification, but EasyPost won't correct an intentionally bad address
Does EasyPost support validation of addresses in US territories?
How can I tell if an address is residential or not?
Does your API support single-line address verification?
Do you support geocoding (i.e. latitude/longitude)?
What does the "Unable to validate Ship To address. Dial-A-Zip error: Address is too ambiguous" error mean?
Why am I receiving a validation error on delivered packages?
How do I validate addresses using the API?
Read our Address Verification Guide to learn more. Once you enable Address Validation with EasyPost, the verifications string of our Address Object will populate with a status. The Address Verification is working, and will automatically verify all addresses whenever and wherever it's enabled.
How can I verify an address and create a shipment in one API call?
You can set the verify or verify_strict parameter for the to_address object on shipment creation, and it will verify the address at the same time.
However, we have found that most users like to create addresses and shipments separately. When an address is created, the address_id can be saved and re-used for many shipments, thus reducing the number of calls you have to make to our API. This is a great solution if you have a substantial number of repeat customers.
As always, implement our API in the way that fits your business best.
How granular is your address verification?
It depends on where the address is. For certain countries, we can get as granular as the housing unit level. View a complete chart on verification granularity by country.
Why is this address not verifying?
The address in question could be outside of our network. We have an extensive list of countries we support, down to the granularity of our verification (city, street, house, or unit). View a complete chart on verification granularity by country.
I enabled address verification, but EasyPost won't correct an intentionally bad address
First, double check to see if you've enabled address verification under the verify attribute in your Address object. If it's not enabled, then the address verification will not work and we'll assume that you've checked the address yourself.
Second, it's important to note that we will not correct an address that has too many errors in it, or if the address has too many correction possibilities because of the errors. We will flag the address as invalid, but we will not provide auto-correction to any address that has:
- Multiple errors in the address (e.g. invalid ZIP and invalid street name in the same address)
- Multiple address possibilities (e.g. a bad address can be interpreted to be two different verified addresses)
We will correct to a reasonable extent, but it's much safer for you if we flag these problematic addresses instead of assuming your intent behind them. The last thing we want to do is suggest the wrong address based on vague errors.
Does EasyPost support validation of addresses in US territories?
Yes we do. Also note, U.S. territories is still considered domestic address verification for us.
How can I tell if an address is residential or not?
In the Address object, include the verifications field as delivery. This should fill out the residential field as true or false.
Does your API support single-line address verification?
Currently our API does not support validation of addresses entered as a single line of text. While it is possible in some cases to provide complete address information in a single line we don't currently have a way to reliably and accurately parse these for all possible address formats.
Because addresses can have such high variance, compounded by the possibility of being mis-entered, for now we have to require that addresses be entered broken up into their component parts.
For example, here are two addresses just within the USA and US territories:
- BOB SMITH Jr., 123 Main Street, SAN FRANCISCO, CA, 94104
- MRS MARÍA SUÁREZ, URB LAS GLADIOLAS ,150 CALLE A, SAN JUAN,PR, 00926-3232
Even between these two addresses, there are too many differences in how each address component is presented. In order to ensure data accuracy, it's simply better to enter address components separately into our API.
Do you support geocoding (i.e. latitude/longitude)?
Yes, we do support geocoding for address verification.
What does the "Unable to validate Ship To address. Dial-A-Zip error: Address is too ambiguous" error mean?
The address isn’t passing USPS address validation, which means your address verification is working. Try double-checking the address to see if there are any errors.
If you absolutely need to force the shipment, set “address_verification = 0” to bypass the address verification and print the label.
Why am I receiving a validation error on delivered packages?
The error is to serve as a warning that the address could not be validated based on the information provided. To avoid this error, try to ensure the address has suite/apartment number data in the street2 string when applicable.
In general, most drivers will know where a package is intended to go based on the recipients name if a suite number is not provided. If not, then the package will not be delivered.