Table of Contents
< All Topics
Print

API & UI – Database

API & UI  Database
How is your database built?

Our address database is architected using validated, USPS-deliverable addresses as its foundation. We exclusively source address data from the United States Postal Service’s authoritative dataset to ensure maximum accuracy, standardization, and deliverability compliance. By leveraging the USPS Address Management System (AMS) and Delivery Point Validation (DPV), we guarantee that every record in our database corresponds to a real, serviceable location officially recognized by the federal postal authority.

This approach allows us to maintain a high-integrity, verifiable dataset — critical for clients who require reliable homeowner or property address information. Addresses that do not appear on the USPS platform are intentionally excluded from our system, as their deliverability and legitimacy cannot be confirmed through official government channels.

Example 1:

  • Consider the address “1002 Tall Grass Dr, Princeton, TX 75407, USA”, which is visible and locatable on platforms like Google Maps. Based on recent satellite imagery and street views, this appears to be part of a new residential development. However, when the same address is entered into the official USPS ZIP Code Lookup Tool, the system returns: “Unfortunately, this information wasn’t found. Please double-check it and try again.”

    This is a common occurrence with newly constructed homes or subdivisions that have not yet been fully registered or provisioned by the USPS. Before an address can be classified as deliverable in the USPS database, several steps must occur:

    • The local developer or municipality must submit the new address information to the USPS.

    • The USPS must formally assign the address within its Address Management System (AMS).

    • A local postmaster must confirm the establishment of delivery routes and mail receptacle placement.

    Until those steps are completed and the address is officially recognized as deliverable, it will not appear in USPS datasets — and by extension, it will not be present in our API database, which relies exclusively on validated USPS address records to ensure data accuracy, reliability, and compliance.

    This approach helps our users avoid reliance on incomplete or speculative address data, especially in high-growth areas where map services may display visual developments ahead of official postal recognition.

 
 

Example 2:

  • Let’s take the address “1041 Co Rd 104, Carthage, TX 75633, USA”, which appears in Google Maps. While this location is identifiable via commercial geolocation platforms, it does not return a valid result on the official USPS ZIP Code Lookup Tool, which states: “Unfortunately, this information wasn’t found. Please double-check it and try again.”

    This discrepancy illustrates a key distinction in how address data is validated. Our database is built exclusively on USPS-confirmed, deliverable addresses, meaning we only include addresses recognized and serviced by the United States Postal Service. Locations such as manufactured, mobile, or modular homes—particularly in rural or unincorporated areas—are often not included in USPS address datasets due to one or more of the following reasons:

    • They may lack individual delivery routes or mail receptacles.

    • They might be classified under a broader rural route or PO Box address.

    • In some jurisdictions, manufactured homes are not recorded in the real property register and are instead tracked through the Department of Motor Vehicles (DMV), which further complicates standardization and deliverability.

    As a result, addresses like the one above are not included in our platform, ensuring that we maintain a clean, verifiable, and USPS-compliant dataset for our clients.