Page tree
Skip to end of metadata
Go to start of metadata


DOTS Address Validation 3 US ("AV3") is a new version of our Address Validation and Address Validation 2 Web services. This service utilizes the latest .Net Framework, WCF, and can be used as a RESTful service or with SOAP. AV3 is designed to take an unstandardized address, validate it against the latest USPS data, and return standardized, deliverable addresses. The service provides corrected information such as the correct street location and zip plus four code, along with parsed address tokens, such as the PMB box number, pre- and post-directionals, county and state codes, and much more.

AV3 can provide instant address verification and correction to websites or enhancement to contact lists.  However, the output from AV3 must be considered carefully before the existence or non-existence of an address is decided.

If you are an existing client and are using the previous version of this service then please click on the following link.

DOTS Address Validation - US 2

Developer Guide Map


This section lists the DOTS Address Validation US 3 operations and goes into the details behind the inputs and outputs. 


GetBestMatches  (Recommended Operation)









GetPossibleMatches (Deprecated) 

ValidateAddressSingleLine (Deprecated) 

GetPossibleMatchesSingleLine (Deprecated) 

DPV Codes, DPV Notes, and Corrections

This section shows additional supporting data tables that are associated to the DOTS Address Validation US 3 operations.


Similar to  the DPV Codes, DPV Notes, and Corrections section, this section reflects details on the error outputs that can happen with the service.

Code Snippets and Sample Code

Here you'll find code snippets for various programming languages and frameworks along with links to our sample code page on the web site.

Try The API

This is where you'll go to take the API for a spin.  There you can test our recommended operation GetBestMatch.

Service Reference

In this section you'll find all the different endpoints supported by this service, input and output schema information as well as an opportunity to try the other endpoints as well.

Frequently Asked Questions

This is a list of some of the questions we hear more often that you can reference and get answers on right away.

Integration Basics

Integrating AV3 into your application should be easy and straightforward. If you are using a common platform, Service Objects may already have sample code built that you can use.

However, if you are using a common platform that does not already have sample code, you can ask Service Objects to build you an example. Email for more details.

Web Service Structure:
Web services are methods that integrate with other applications via the web, and encapsulate tricky business logic. Web services are too large of a topic to cover in this document, but Service Objects has developed its web services to be as easy to integrate and as accessible as possible.

AV3 is a public XML web service that supports SOAP, POST and GET operations, using RESTful paradigms or simple HTTP transport calls.

The host path, or physical location of the web service is here:

A test page for the recommended operation can be found here:
AV3 - Try The API

See the service references and try the other operations here:
AV3 - Service Reference

The location of the WSDL, or Web Service Definition Language document, is here (This is also accessible via the "Service Definition" link.): 

Important Notes!

  1. This XML is the definition of the web service, meaning its inputs, outputs, operations, and the like. Most likely, you will have another tool read this WSDL and make the operations available to you in your application. Whenever your utilities or IDE asks for a WSDL path to AV3, you can provide this one.

  2. SOAP is done via POST, only with special XML markup in the post-body.

Every web service has operations that it offers to subscribers – methods that do different work and return different output. Examining the link above, you will notice several of these operations available, which are described in detail later on.

  • No labels