Quick-Start Guide
Address Validation 3 (AV3) for Snowflake: Quick-Start Guide
From install to your first validated address in under 10 minutes β validate, correct, and standardize US addresses directly in SQL, inside your Snowflake account.
π 6 steps Β· SQL only
β No credit card required
Get AV3 on the Snowflake Marketplace β
What this guide covers
Address Validation 3 (AV3) is a Snowflake Native App from Service Objects that validates, corrects, and standardizes US addresses to the USPS standard β without moving your data out of Snowflake. In this quick start you will:
- Install AV3 from the Snowflake Marketplace and start a free 20-day trial (1,000 validations, full
GetBestMatchesoutput). - Grant the one external access integration AV3 needs.
- Run
AV3_VALIDATEon a table or aSELECTquery. - Read standardized addresses, DPV confirmation, ZIP+4, RDI, and correction notes back in SQL.
Before you start
You need:
- A table containing the US addresses you want to validate (or use the sample data below).
- A Snowflake account in a supported region β AWS: US East (N. Virginia), US East (Ohio), US West (Oregon); Azure: Central US (Iowa), and others listed on the Marketplace.
Get the app from the Snowflake Marketplace
Already installed the AV3 app and started your trial? Skip to Step 2.
If not: open the AV3 listing on the Snowflake Marketplace and select Try Now to start the free 20-day trial.
The trial includes 1,000 address validations with full GetBestMatches output including DPV codes, correction notes, and standardized fields. No credit card required.
Grant the external access integration
After installation, AV3 needs permission to connect to the Service Objects address validation API. This is the only external connection the app requires.
The external access integration connects the AV3 Native Application to the Service Objects Address Validation API. You grant it explicitly, you can see exactly what it accesses in the app manifest, and you can revoke it at any time.
Prepare your address data
You can validate any table containing US addresses. The input should include the following columns β if your table uses different names, create a VIEW that maps your columns to these names.
| Column | Required? | Example |
|---|---|---|
CONSUMER_ROW_ID |
Recommended | 1 |
BUSINESSNAME |
Optional | Acme Corp |
ADDRESS |
Required | 123 Main Stret |
ADDRESS2 |
Optional | Suite 400 |
CITY |
Conditional | Los Angelos |
STATE |
Conditional | CA |
POSTALCODE |
Conditional | 90012 |
CONSUMER_ROW_ID is a unique identifier for each record. It is carried through to the output so you can join validated results back to your source table.
Sample data to test with
If you want to test before using your own data, create a sample table:
Run your first validation
There are three ways to call AV3_VALIDATE. Start with Option B or C using the sample data β once you see the results, run it on your own table.
Option A β Validate an entire table
Bind your table and call AV3_VALIDATE. Results are saved to APP_CODE.AV3_ADDRESS_RESULTS.
Option B β Validate from a SELECT query
Pass a query directly to validate any subset of records without creating a separate table.
Option C β Validate and save to a custom output table
Pass a query and an output table path. A timestamped table is created in your schema with full validation results.
Read the results
Query the output table to see the validated addresses:
Or return only the records where AV3 confirmed a valid, deliverable address:
What the results include
| Field | What it tells you |
|---|---|
| Standardized address | The corrected, formatted address components, standardized to the USPS standard for mailing addresses. |
| DPV | Whether the address is a confirmed USPS delivery point. |
| DPV Notes | Codes explaining what was found or corrected at the delivery-point level. |
| ZIP+4 | The full nine-digit ZIP code. |
| RDI | Residential vs. commercial classification. |
| Correction notes | What AV3 changed and why. |
| Address fragments | The address broken down into its smallest parts. |
Sample input β output
| Field | Input | Output |
|---|---|---|
| Address | 26 S Chestnut | 26 S Chestnut St |
| Address 2 | β | β |
| City | Ventura | Ventura |
| State | CA | CA |
| ZIP Code | 93033 | 93001-2800 |
| DPV | β | 1 |
| DPV Desc | β | Yes, the input record is a valid mailing address |
| Is Residential | β | FALSE |
| Barcode digits | β | 930012800269 |
| Corrections Desc | β | Directional or Suffix change, ZIP code change |
Use the output in your workflows
With validated results in a Snowflake table, you can:
- Join validated addresses back to your source table by row ID.
- Filter by
DPVto separate confirmed addresses from bad or partially correct ones. - Route records based on DPV Notes: correct and proceed, flag for manual review, or suppress.
- Feed standardized addresses into downstream pipelines, ML models, or CRM syncs.
- Schedule recurring validation by wrapping the
CALLin a Snowflake task.
Trial & pricing
The free trial includes 1,000 address validations over 20 days with full GetBestMatches output. At the end of 20 days or 1,000 records (whichever comes first), the trial stops β with no automatic charges.
Standard
- 100,000 validations included
- Full
GetBestMatchesoutput - Marketplace Capacity Drawdown (MCD) supported
Enterprise
- 500,000 validations included
- Full
GetBestMatchesoutput - Marketplace Capacity Drawdown (MCD) supported
Frequently asked questions
Need help?
Our team is here to get you from trial to production.
support@serviceobjects.com
ae@serviceobjects.com