New 42-day free trial Get it now
Smarty

Improving address form completion rates—whether in a shopping cart, request for quote, or other form—can be a sinch if you’re using an address autocomplete tool. Not sure what that is? When you see an address line on a form and think “oh shoot this is going to take a minute” and then it fills it in after only a few keystrokes, that’s address autocomplete.

And no, not all address autocomplete tools are created equal.

Some check against their own address database only that is not frequently maintained. Some are only checked against the United States Postal Service database so they do not include non-postal addresses. And most do not have any sort of customization options when it comes to utilizing their APIs.

Smarty’s US Autocomplete Pro API checks against our incredibly large database of over 210+ million USPS addresses in addition to over 20 million non-postal addresses, and it is highly customizable.

Customizing for geolocation

One typical use for US Autocomplete is to assist an end user in entering their own address. In this case, you likely want to provide suggestions that are close to the user's location. The Geolocation feature, which is turned on by default, does just that. It uses data that maps the user's IP address to a city or surrounding area. It then places their city and state into the prefer_cities field.

Customizing for preferences

Another use for Autocomplete is for call centers where you may want to prefer suggestions that are in specific cities, states, or ZIP Codes. When set, these results will occupy the top percentage (prefer_ration) of the results.

Examples:

  • prefer_cities=SEATTLE, REDMOND,WA; RENO, NV
  • prefer_states=CO; OK
  • prefer_zip_codes=84660; 90210&prefer_geolocation=none

Customizing with include filters

Sometimes, you want to limit results to only specific cities, states, or ZIP Codes. This is different from preferences, which could provide suggestions outside your preference areas. Filters will only show suggestions that match the filter. Note that there are some keywords you can use for states that will filter on the 48 contiguous states (including DC), which exclude territories, Alaska and Hawaii. Or all states which exclude just the territories.

As with preferences, if you use the ZIP Code filter, you cannot use any other preference or filter.

Customizing with exclude filters

If you need to exclude specific states from your results, you can use this filter. It cannot be used with any other filter or the geolocation preference, but it works with other preference settings.

Customizing the source

US Autocomplete Pro has included non-postal addresses for a little over 6 months. Non-postal addresses are those that USPS won’t deliver to, but are valid physical addresses. By default, only postal addresses will be returned.

Set this to “all” if you also want to return non-postal addresses. You will know if a result is a non-postal address if it contains the source field with the value of “other.”

Customizing a selected secondary

This parameter gets it name from when a user selects an address to drill down on a particular secondary. This is the most complicated one of the options discussed in the webinar, but I’ll do my best to summarize.

If the address submitted is an apartment building with 100 units, this will dictate how many of those units there are and if the user can drill down to an exact unit. You can learn more about it in the recording below, beginning at 18:40.

View the webinar recording

This is just a brief overview of what was covered. You can view the full 26 minute video below.

Subscribe to our blog!
Learn more about RSS feeds here.
Read our recent posts
Functional options pattern in Go: Flexibility that won’t make future-you sigh loudly
Arrow Icon
SDK authors live in a permanent tug-of-war:Users want a simple constructor they can paste and ship. Maintainers want room to grow without breaking everybody’s build on the next release. That second part matters a lot right now, because a lot of people are still relatively early in their software careers. Approximately one in three developers has coded professionally for four years or less. That matters because unclear or fragile APIs disproportionately hurt newer developers—they don’t have scars yet.
Ambiguous address matches: What they are and why compliance teams should care
Arrow Icon
If you’ve ever run into an address that seems to exist in more than one place, congratulations—you’ve discovered the world of ambiguous address matches. They’re the Schrödinger’s cat of location data: valid, yet potentially two distinct locations. This blog will focus on a few key things: What are ambiguous address matches?Why ambiguous address matches matter for compliance and customer serviceHow to handle matches with address ambiguityWhy you should inform your customers of ambiguous address matchesOur final thoughts on ambiguous address matchesWhat are ambiguous address matches?An ambiguous address match occurs when an entered address resolves to two or more valid locations with slight but meaningful differences.
Smarty's January 2026 release adds parcel boundaries, provisional addresses, and smarter international geocoding
Arrow Icon
OREM, UT, Jan 27, 2026—Smarty®, an expert in address data intelligence, today announced a three-part release designed to help organizations turn messy, fast-changing location data into operational confidence. The January 2026 bundle introduces: 1) A brand-new parcel dataset, 2) Expands provisional address programs into core U. S. products, and 3) Upgrades Smarty’s International Geocoding engine—giving organizations more precision and more usable signals for automation at scale. “Address data is never ‘done.

Ready to get started?