ZIP+4, Address Verification, Address Correction, Address Standardization API for .NET

ZIP+4 Address Verification and Correction API

NetZipCode for .NET allows you to quickly and easily build ZIP Code lookup, address verification plus address correction and parsing into your custom applications. The delivery address is checked for proper Postal Service format and standardized if necessary. Spelling corrections are made and the address is split into USPS standard components. One year USPS database subscription is included.

	● Address Verification - Point-of-entry or batch address validation.
	● Address Correction - Correct spelling errors, standardize addresses and append ZIP+4.
	● Address Parsing - Separate address and city/state/zip into their discreet elements.
	● Unlimited Processing Volume - No processing limits or restrictions with the included USPS database.

x64 Version Available

^$599	Single-Database License	Download Evaluation (10.6 MB)
^$1199	5-Database License	User's Guide
^$1899	10-Database License	View Cart

To minimize download time,
this evaluation is for
Orlando, Florida only

Orlando Sample Addresses

A Closer Look

How NetZipCode Works


			NetZipCode for .NET follows the US Postal Service “one component failure rule” to find a correct address match. This rule permits an address match if no more than one address component mismatch exists, where a “component” is defined as a predirectional, street name, street suffix, or a postdirectional. Consider the following address: 100 E MAIN ST N This address has all four components. If one of the components has to be added, changed, or deleted to achieve a unique match, NetZipCode will correct the address and return the ZIP+4. Under current USPS address matching rules, if more than one component is incorrect, no match is allowed. If adding, changing or deleting a component results in multiple matches, no match can be returned. The priority is to add a suffix first, before adding a directional. If there is no match, change or delete the suffix. Finally, change or delete a directional. If there is no exact address match within the city, NetZipCode applies the “one component failure rule” within the input ZIP code. If there is still no match, then NetZipCode applies the “one component failure rule” to all addresses within the postal finance number. If there is still no match, the address is rejected. An array of flags is returned for each address giving you important information about the status of the matching process such as why the matching failed or what corrections were necessary in order to achieve a match. Also returned is the Address Type allowing you to identify Street, Military, PO Box, Rural Route, Highway Contract or General Delivery addresses and process them accordingly.
	The screen shot above was taken from a sample application created using VB.NET. Other samples, including C#, can be found in the NetZipCode folder.		NetZipCode for .NET uses both Soundex and Phonetic matching algorithms to find matches that other programs often miss.