Reference · built on requestConnectorShipping & logistics

UPS

Tracking, Track Alert webhooks, rating, time in transit, shipping, and pickups from the UPS APIs under OAuth 2.0.

Request accessPricing ↗

About

UPS publishes its Rating, Shipping, Tracking, Time In Transit, Pickup, and Address Validation APIs on the UPS Developer Portal, with OpenAPI specifications mirrored in the UPS-API GitHub organization. The Track API returns package activity, expected delivery dates, and UPS Access Point details for a 1Z number or a reference number. The UPS Track Alert API pushes event updates to your webhook for subscribed tracking numbers, so nothing has to poll.

Through Fibric, an operator subscribes your outbound packages to Track Alert, matches each event to the order it belongs to, and proposes the next step when a package stalls, is redirected to an Access Point, or misses its expected delivery date.

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

Inputs

  • Current status, activity history, and delivery details for a package via GET /track/v1/details/{inquiryNumber}
  • Tracking by reference number, and per-package tracking for a multi-piece shipment
  • Pushed event updates for subscribed tracking numbers through the UPS Track Alert API v2, up to 100 numbers per request
  • Rated or shopped service options and charges from the Rating API, including negotiated rates
  • Estimated delivery times between two locations from the Time In Transit API
  • Street-level address checks against the United States Postal Service database for the U.S. and Puerto Rico
  • Pickup status (received, dispatched, completed, cancelled) from the Pickup API

Proposed actions

  • Target capability: propose a shipment through POST /shipments/{version}/ship and return the label and 1Z tracking number for review
  • Target capability: propose voiding a shipment through Void Shipment by its shipment identification number
  • Target capability: propose an on-demand pickup through Pickup Creation, or cancel one by its pickup request number
  • Target capability: propose a Track Alert subscription for a batch of tracking numbers so events arrive by webhook

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

What you can build

  • Sync carrier events to the order record

    Subscribe each new 1Z number to Track Alert. As events arrive, propose the status update on the order and the customer-facing note.

    With Tracking Sync

  • Recover a missed delivery

    When an event shows a delivery attempt or an Access Point hold, propose the customer notice with the pickup location and the hold deadline.

    With Missed Delivery, Pickup Expiry

  • Audit invoiced charges against rated charges

    Compare the negotiated rate returned at ship time with the charge that later appears on the invoice and propose a dispute where they differ.

    With Freight Audit

Requirements

  • A UPS account number and a UPS Developer Portal app with a Client ID and Client Secret
  • The Customer Integration Environment (wwwcie.ups.com) for testing before onlinetools.ups.com
  • A public HTTPS endpoint, with webhook credentials managed on the portal, to receive Track Alert events
  • Transaction ID and transaction source values on every tracking request
Authentication
OAuth 2.0: POST /security/v1/oauth/token with Client ID and Client Secret over Basic auth. Client credentials when you are the shipper; an authorization code flow when you ship on another party's account.

Limits

  • Tracking data is rolled off after a 120-day retention period and may not be returned afterward
  • Track Alert rejects any submission of more than 100 tracking numbers
  • Street Level Address Validation covers the U.S. and Puerto Rico only; in the test environment it returns results only for NY and CA
  • Client credentials tokens work only when the integration owner is also the UPS shipper

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request UPS ↗

Questions and answers

Does UPS support webhooks for tracking?
Yes. The UPS Track Alert API v2 takes a list of tracking numbers, creates a subscription for each, and pushes event updates to the webhook you register. Submissions are limited to 100 tracking numbers at a time. Webhook credentials are managed on the UPS Developer Portal.
Which OAuth flow does UPS use?
Client credentials when the integration owner is also the UPS shipper: send Client ID and Client Secret to POST /security/v1/oauth/token, optionally with the 6-digit account number in x-merchant-id. An authorization code flow exists for shipping on another party's account.
How long does UPS keep tracking history?
The Track API states data is rolled off after a 120-day retention period and may not be returned afterward. Store the events you need on the order record as they arrive.
Ask about UPS

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with UPS through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy