United States Postal Service · Authentication Profile

United States Postal Service Authentication

Authentication

United States Postal Service secures its APIs with http and oauth2 across 4 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

GovernmentPostal ServiceShippingLogisticsAddress ValidationPackage Tracking
Methods: http, oauth2 Schemes: 4 OAuth flows: authorizationCode, clientCredentials API key in:

Security Schemes

OAuth oauth2
· flows: clientCredentials, authorizationCode
OAuth oauth2
· flows: clientCredentials
BasicAuth http
scheme: basic
BearerTokenAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑
generated: '2026-11-11'
method: searched
source: https://developers.usps.com/getting-started; openapi/usps-addresses-openapi.yml, openapi/usps-adjustments-openapi.yml,
  openapi/usps-appointments-openapi.yml, openapi/usps-carrier-pickup-openapi.yml, openapi/usps-containers-openapi.yml, openapi/usps-domestic-labels-openapi.yml,
  openapi/usps-domestic-prices-openapi.yml, openapi/usps-informed-delivery-mail-campaigns-openapi.yml, openapi/usps-informed-delivery-package-campaigns-openapi.yml,
  openapi/usps-international-labels-openapi.yml, openapi/usps-international-prices-openapi.yml, openapi/usps-international-service-standards-openapi.yml
  ...
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: OAuth
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: /oauth2/v3/token
    scopes: 1
  - flow: authorizationCode
    authorizationUrl: /oauth2/v3/authorize
    tokenUrl: /oauth2/v3/token
    scopes: 1
  description: The specified APIs accept an access token formatted as a JSON Web Token. The relative path to the OAuth2 version
    3 API which supplies this access token is provided below for reference.
  sources:
  - openapi/usps-addresses-openapi.yml
  - openapi/usps-adjustments-openapi.yml
  - openapi/usps-appointments-openapi.yml
  - openapi/usps-carrier-pickup-openapi.yml
  - openapi/usps-domestic-labels-openapi.yml
  - openapi/usps-domestic-prices-openapi.yml
  - openapi/usps-international-labels-openapi.yml
  - openapi/usps-international-prices-openapi.yml
  - openapi/usps-locations-openapi.yml
  - openapi/usps-logistics-shipments-openapi.yml
  - openapi/usps-ncoa-openapi.yml
  - openapi/usps-pmod-openapi.yml
  - openapi/usps-qr-codes-openapi.yml
  - openapi/usps-reconciliation-adjustments-openapi.yml
  - openapi/usps-scan-forms-openapi.yml
  - openapi/usps-service-standards-files-openapi.yml
  - openapi/usps-service-standards-openapi.yml
  - openapi/usps-ship-enrollment-openapi.yml
  - openapi/usps-subscriptions-addresses-openapi.yml
  - openapi/usps-subscriptions-adjustments-openapi.yml
  - openapi/usps-subscriptions-disputes-openapi.yml
  - openapi/usps-subscriptions-ncoa-openapi.yml
  - openapi/usps-subscriptions-package-transaction-details-openapi.yml
  - openapi/usps-subscriptions-tracking-openapi.yml
  - openapi/usps-subscriptions-tracking-v3r2-openapi.yml
  - openapi/usps-subscriptions-unpaid-packages-openapi.yml
  - openapi/usps-tracking-openapi.yml
  - openapi/usps-tracking-v3r2-openapi.yml
  - openapi/usps-userinfo-openapi.yml
- name: OAuth
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: /oauth2/v3/token
    scopes: 1
  description: The specified APIs accept an access token formatted as a JSON Web Token. The relative path to the OAuth2 version
    3 API which supplies this access token is provided below for reference.
  sources:
  - openapi/usps-containers-openapi.yml
  - openapi/usps-informed-delivery-mail-campaigns-openapi.yml
  - openapi/usps-informed-delivery-package-campaigns-openapi.yml
  - openapi/usps-international-service-standards-openapi.yml
  - openapi/usps-payments-openapi.yml
  - openapi/usps-service-standards-directory-openapi.yml
  - openapi/usps-shipping-options-openapi.yml
- name: BasicAuth
  type: http
  scheme: basic
  description: Use the client_id and client_secret for the username and password, respectfully. The client application is
    authenticated using the Basic authentication security scheme.
  sources:
  - openapi/usps-oauth-openapi.yml
- name: BearerTokenAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: An access token is used to authenticate the client application making the request.
  sources:
  - openapi/usps-oauth-openapi.yml
docs: https://developers.usps.com/getting-started
docs_summary: Create an app in the USPS Customer Onboarding Portal (COP); pass its Consumer Key and Consumer Secret as client_id
  and client_secret to the OAuth API; all USPS APIs require the token in the Authorization header using the Bearer Token scheme.
  Labels APIs additionally take an X-Payment-Authorization-Token from the Payments API.

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/usps-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.