USPS
The United States Postal Service (USPS) provides a modern suite of RESTful APIs for address validation, domestic and international pricing, shipping label creation and cancellation, tracking, and service standards through its developer portal. The APIs replace the legacy Web Tools platform and use OAuth 2.0 Client Credentials for authentication. The platform supports both production and TEM (Testing Environment for Mailers) endpoints for developing and validating shipping integrations.
USPS publishes 5 APIs on the APIs.io network. Tagged areas include Shipping, Postal, Address Validation, Tracking, and Labels.
USPS’s developer surface includes documentation, getting-started guide, signup flow, GitHub presence, engineering blog, and 3 more developer resources.
Kin Score
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
USPS OAuth 2.0
Token endpoint for OAuth 2.0 Client Credentials authentication used to authorize requests to all USPS API products.
USPS Addresses API
Verify and standardize US addresses to USPS specifications, reducing shipping delays and errors.
USPS Tracking API
Retrieve tracking status and delivery events for shipped packages across USPS services.
USPS Labels API
Create and cancel domestic shipping labels with integrated address standardization, pricing, and manifesting.
USPS Domestic Prices API
Retrieve current pricing information for USPS domestic shipping products and services.
GraphQL 1
GraphQL schemas published by this provider.
USPS GraphQL Schema
Conceptual GraphQL schema for the United States Postal Service (USPS) APIs. This schema models the capabilities exposed by the USPS REST API developer portal at [https://develop...
GRAPHQLSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 3
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/usps"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/usps/operations?limit=25"
curl "https://apis.io/api/v1/providers/usps/evidence"
Discovery needs no key. Ratings and market analysis are Pro.