- Front-End Web and Mobile
- Amazon Location Service
- Bulk address validation
Bulk address validation
Amazon Location Service bulk address validation helps you verify that customer addresses are real, correctly formatted, and deliverable. Submit address records in bulk for asynchronous processing — the service validates formatting, corrects common errors like misspellings and missing postal codes, standardizes addresses to match postal authority conventions, and returns a match confidence score and deliverability indicators for each record. Address validation currently supports addresses in the United States, Canada, Australia, and United Kingdom with country-specific postal attributes.
What is address validation?
How It Works
Validate address data in bulk through a simple workflow
Prepare your address data
Format your addresses as Apache Parquet files. You can use free-form address lines or structured address components (street, city, state, postal code, country), or a combination of both. Upload the files to an Amazon S3 bucket.
Start a validation job
Call the StartJob API with the ValidateAddress action. Specify your S3 input and output locations and an IAM execution role. Optionally request additional features like geographic coordinates (Position) or country-specific postal attributes (CountrySpecificAttributes).
Monitor and retrieve results
Use GetJob to check job status. When the job completes, download the results from your S3 output bucket. Each record includes the standardized address, a match confidence score, deliverability indicators, and component-level validation status showing which parts were validated, corrected, or unconfirmed.
Key benefits
Use Cases
How your business can verify addresses, reduce failed deliveries, and improve data quality at scale.
Validate patient and provider addresses to support accurate claims processing, care coordination, and administrative reporting. Clean, standardized address data reduces billing errors and helps ensure critical communications reach the right recipients. An automated address check at ingestion prevents bad data from entering your systems in the first place.
Standardize customer addresses across your portfolio to support identity verification, risk assessment, and fraud prevention workflows. Bulk address verification helps maintain consistent, reliable address data across large customer databases — reducing exposure from inaccurate or incomplete records. Supports international address validation across the United States, Canada, Australia, and the United Kingdom.
Validate mailing addresses before dispatching routes to reduce failed last-mile deliveries and improve operational efficiency. Standardized addresses support downstream routing and optimization workflows across your delivery network. Postal address verification confirms each address is real and deliverable before it enters your dispatch queue.
Perform one-time address cleansing during system transitions, or run regular validation jobs to maintain data quality over time. The address validation API processes your records in bulk, working as an address corrector that fixes formatting errors, fills missing components, and standardizes every record. Ideal for CRM cleanup, entity resolution, and analytics workflows that depend on consistent, structured address data.
Reduce shipping failures and fulfillment costs by validating and standardizing customer addresses before orders are dispatched. Verify mailing addresses against authoritative postal data so your system catches errors before they reach fulfillment. Clean address data means fewer failed deliveries, fewer returns, and a better customer experience.
Frequently Asked Questions
Page topics
What is the difference between address validation and address verification?
Address validation checks whether an address is properly formatted, complete, and matches a known postal format. Address verification goes further — it confirms the address exists as a real, deliverable location in authoritative postal databases. Amazon Location Service handles both in a single job. The service validates formatting and completeness, then verifies the address against postal authority data and returns a match confidence score and deliverability indicators (Mailable and Locatable) for each record.
What is the difference between address validation and geocoding?
Both can improve address data quality, but they work differently. Geocoding converts an address into geographic coordinates and standardizes the format in the process — it normalizes components, corrects formatting, and adds postal code details. Address validation goes further by checking whether an address is real and deliverable against authoritative postal data, returning a match confidence score and deliverability indicators. Use geocoding when you need coordinates and standardized formatting. Use address validation when you need to confirm an address can receive mail or packages. You can optionally request geographic coordinates as part of address validation results by enabling the Position feature.
How do I validate addresses with Amazon Location Service?
Prepare your address data as Apache Parquet files and upload them to an Amazon S3 bucket. Call the StartJob API with the ValidateAddress action, specifying your input and output S3 locations. The service processes your addresses asynchronously and writes validated results back to S3. Use GetJob to monitor progress and download results when the job completes.
What countries does address validation support?
Address validation currently supports addresses from Australia, Canada, United Kingdom, and the United States. Each country includes country-specific attributes — for example, US addresses receive carrier route and delivery point codes, while Australian addresses receive delivery point identifiers and GNAF PIDs.
How does address validation correct errors?
The service identifies and corrects common address errors including misspellings, missing postal codes, incorrect formatting, and non-standard abbreviations. Each corrected component receives a status detail showing what happened — Exact match, Corrected, Alias matched, Appended from reference data, or Not Found. The output includes the standardized address formatted according to regional postal conventions alongside the original input, so you can see exactly what changed.