How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

United States Postal Service Addresses API

Address validation and standardization operations

United States Postal Service Addresses API is one of 12 APIs that United States Postal Service publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 9 JSON Schema definitions.

Tagged areas include Addresses. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 9 JSON Schemas.

This API exposes 3 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 3.0.

Requests are made against 2 base URLs: https://apis.usps.com, https://apis-tem.usps.com.

3 operations 3 paths 4 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.0
Base URL
https://apis.usps.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

United States Postal Service Addresses API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 Bearer Token obtained from the USPS OAuth API.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Addresses 3

Address validation and standardization operations

GET
/addresses/v3/address
USPS Addresses Validate Address
validateAddress 6 params → 200400401429500
GET
/addresses/v3/city-state
USPS Addresses Get City and State by ZIP
getCityState 1 param → 200400401
GET
/addresses/v3/zipcode
USPS Addresses Get ZIP Code
getZIPCode 4 params → 200400401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Address (16 properties), ZIPCodeResult (5 properties), CityState (3 properties), Error (2 properties). Each schema is shown below with its type and property counts.

ZIPCodeResult
object
ZIP Code lookup result.
5 properties
CityState
object
City and state lookup result.
3 properties
Error
object
API error response.
2 properties
Address
object
USPS standardized address response.
16 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

united-states-postal-service-addresses-api-openapi.yml Raw ↑

Other APIs United States Postal Service publishes across the network.

USPS International Prices API
USPS Domestic Labels API
USPS International Labels API
USPS Locations API
USPS Service Standards API
USPS Shipping Options API
USPS SCAN Forms API
USPS OAuth API
United States Postal Service Carrier Pickup API
United States Postal Service Domestic Prices API
United States Postal Service Tracking API
Where this information came from

This is an independent, third-party profile of United States Postal Service Addresses API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.