APIs

This API supports returning destination entry facilities (i.e., drop off locations) for a given ZIP Code to enable Parcel Select Destination Entry, USPS Connect, and Parcel Select Lightweight. This API also provides additional information about working hours, delivery type, mail class, shape, palletization, and facility type.

The Drop-Off Locations API enables businesses using USPS Connect products/services to determine the most convenient USPS location at which to drop off their packages and mail.

Your exclusive access to USPS APIs is protected using OAuth 2.0 industry standards.

All USPS APIs require an OAuth 2.0 access token to be conveyed in the 'Authorization' header, using the 'Bearer' token scheme.

Once you sign-in to the API developer portal, you may get the OAuth credentials you will need to register your application 'Add App'. See "Getting Started" for further information about: signing-in, registering your application, and additional USPS account credentials you will need to integrate your application with USPS APIs.

You are responsible for securing the application credentials once issued. Please contact USPS if your credentials have been disclosed to external parties and we will issue new credentials.

This API allows for the creation of Priority Mail Open and Distribute (PMOD) and Priority Mail Express Open and Distribute (PMEOD) labels and containers.  The Open and Distribute service is an option for mailers to bundle their shipments into a single package/container which will be opened and sorted at the destination facility.

The API will create the PMOD/PMEOD label and the 99M form required for mailing.  Items can be added to the Open and Distribute container and closed when ready for manifest.

Caches payment account information so that it is entered once then used to create multiple labels. 

Shipment Confirmation Acceptance Notice(SCAN) form allows integrators to link multiple domestic and international labels through one Electronic File Number (EFN) and physical SCAN Form (PS Form 5630 or 3152). 

This API supports the service standards for the number of days between the acceptance and delivery of a piece of mail that the Postal Service™ considers to be timely delivery. Service standards are delivery benchmarks for how long customers can expect for the Postal Service to deliver different types of mail from origin to destination — Point A to Point B. Service standards are not necessarily the same as the actual service performance.

The Service Standards File Download API provides an efficient way for mailers to download Service Standards files so they can be consumed programmatically and not require manual intervention.

The Ship Enrollment API allows a user to check if their MID is enrolled in USPS Ship. If enrolled, the enrolled programs (such as Outbound and Returns) and the date the MID was enrolled will be returned in the response.

Receive a comprehensive list of pricing, service standards, and shipping options for USPS products within a single API call.

This API allows customers to create and manage their subscriptions for any adjustments on their packages.  This also includes the listener endpoint specifications for the webhook to receive adjustment event notifications per package.

Adjustments are any changes or discrepancies detected in the mailstream against a package's manifested characteristics that affect the package's pricing.  For example, if a package was manifested with one weight and mailed with another, an adjustment may be issued for the difference in pricing.

This API allows customers to create and manage their subscriptions for any disputes on their packages.  This also includes the listener endpoint specifications for the webhook to receive dispute event notifications per package.

Disputes are filed when a postage adjustment needs to be reviewed. For example, if discrepancies were detected by mail processing equipment and an adjustment was issued, a dispute can be filed to review the detected pricing discrepancy. If the dispute is granted, the pricing will be adjusted based on the results of the dispute.

Create a subscription to receive tracking events by mailer ID or tracking number. Manage all tracking subscriptions, in one place, by providing your server URL to receive Postal Service tracking events.  This also includes the listener URL specifications for the webhook to receive tracking notifications per package.