UPS

Rate, rate-shop, validate addresses, track, check transit times, find locations and create UPS shipments with labels.

Quote UPS rates and transit times in order flows, create labels from fulfilment systems and push tracking milestones to customers.

Build a flow with UPS Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

address validations

Validate address
Source
Street-level address validation and residential/commercial classification (US and Puerto Rico).
address_validations.search

locations

Find UPS locations
Source
UPS Access Points and drop-off locations near an address.
locations.search

rates

Rate or shop UPS services
Source
Rate one service or shop all services for a shipment, optionally with time in transit. Quotes are not billed.
rates.search

shipments

Create shipment and label
Destination
Not retried automatically
Approval before production
Create a UPS shipment and return tracking numbers, charges and labels. Billable in production.
shipments.create

tracking

Track package
Source
Status, delivery dates and scan activity for a UPS tracking number.
tracking.get
Track by reference
Source
Track packages by a shipment reference number.
tracking.search

transit times

Time in transit
Source
UPS services with delivery dates and transit days between two locations.
transit_times.search

Authentication

UPS developer app client ID and secret (OAuth client credentials)

Plans and access

Requires a UPS.com profile, a developer app with the Rating, Address Validation, Tracking, Time in Transit, Locator and Shipping products, and a UPS shipper account for rates and labels. Negotiated rates and shipping need the shipper number linked to the app. Address Validation Street Level covers the US and Puerto Rico only.

Test environment

The Customer Integration Environment (wwwcie.ups.com) uses the same app credentials and returns test data; CIE labels are not billed.

Rate limits

UPS applies per-app transaction limits; HTTP 429 when exceeded. Tracking and Address Validation have daily volume guidance per app.

Pagination

Single responses; tracking returns all packages for an inquiry number.

Provider events

Track Alert subscriptions push tracking events (separate Track Alert product). Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

shipments.create is billable and UPS has no idempotency key; Nexra never retries it. Voiding shipments, pickups and paperless document uploads are not implemented.
UPS has no list endpoints; every operation is a lookup or a quote.
Complex request objects (Shipment, Package) follow the UPS JSON schema and are passed through after structural validation.
The health check validates UPS's documented sample address (26601 Aliso Creek Road, Aliso Viejo CA 92656), so the app needs the Address Validation product.
UPS JSON returns single elements as objects instead of arrays; Nexra normalises them to arrays.
The date format for reference tracking (fromPickUpDate, toPickUpDate) is not documented; values are passed through as entered.

Developer reference

Create the United Parcel Service credentials described above with the narrowest permissions your flows need.
In Nexra, open Connect, then Connections, then New connection, choose UPS, enter its settings and credentials, and tick only the write actions you need. Connection guide
Test the connection, then use its actions as flow sources and destinations. Flow guide

United Parcel Service docsAPI reference United Parcel Service docsAuthentication

Machine-readable detail: GET /api/public/connect/connectors/ups and the Connections API.