Reference · built on requestCommons signalPlaces & geographic reference

USPS Addresses 3.0 API

Validates and standardizes US postal addresses, ZIP+4 codes, and city/state mappings via the USPS Addresses 3.0 REST API.

About

The United States Postal Service provides the Addresses 3.0 API on the modern USPS Developer Portal to help shippers and businesses cleanse and verify domestic postal addresses. The RESTful service checks addresses against the USPS Delivery Point Validation database, corrects street abbreviations and casing, appends accurate 5-digit ZIP Codes and ZIP+4 extensions, and resolves city and state names.

Through Fibric, an operator monitors incoming shipping addresses across customer orders, proposing standardized street addresses and corrected postal codes before orders enter fulfillment.

This is a reference listing. It documents what Fibric would read from USPS Addresses 3.0 API and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Standardized street address, secondary unit, and ZIP+4 code via POST /addresses/v3/address
  • City and state resolution for 5-digit ZIP Codes through POST /addresses/v3/city-state
  • ZIP Code and ZIP+4 lookup by street address and city from POST /addresses/v3/zipcode
  • Delivery Point Validation (DPV) confirmation codes indicating deliverable address status
  • Carrier Route codes and delivery point barcodes for bulk postal sorting compliance

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Standardize shipping addresses prior to label purchase

    When customer checkout addresses contain typo errors or missing suite numbers, propose standardized street addresses and valid ZIP+4 codes before label generation.

    With Address Repair, Ship-To Change

  • Resolve ambiguous postal codes on customer orders

    Cross-reference mismatched city, state, and postal code entries against USPS city-state endpoints, proposing corrected 5-digit ZIP Codes for customer orders.

    With Address Repair

  • Prevent delivery exceptions from undeliverable addresses

    Flag orders whose address validation yields negative DPV confirmation, proposing customer address verification outreach before shipments leave the warehouse.

    With Missed Delivery, Carrier Exception

Requirements

  • A registered account on the USPS Developer Portal with an approved Addresses 3.0 API app
  • OAuth 2.0 access token passed as an Authorization Bearer header in HTTPS requests
  • Domestic US street address components including street line, city, state, or ZIP Code
Authentication
OAuth 2.0 Client Credentials token obtained using a Consumer Key and Consumer Secret from the USPS Developer Portal.

Limits

  • The API validates domestic United States, APO/FPO, and US territory addresses only
  • Developer portal apps are bound by transactional request rate limits and concurrency caps
  • Addresses must be valid postal delivery points recognized in the national address directory

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request USPS Addresses 3.0 API ↗

Questions and answers

How does Addresses 3.0 differ from legacy USPS Web Tools?
Addresses 3.0 is a modern REST API on the USPS Developer Portal utilizing JSON payloads and OAuth 2.0 authentication, replacing the legacy XML-based Web Tools interface.
What is DPV confirmation in the API response?
Delivery Point Validation confirms whether a specific address is a deliverable location where mail carriers make deliveries, distinguishing confirmed delivery points from invalid addresses.
Are there costs to use the USPS Addresses API?
Registration and API access on the USPS Developer Portal are free for domestic shipping and mailing verification purposes, subject to acceptable use policies.
Ask about USPS Addresses 3.0 API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.