UPS Shipping API Knowledge Patch
Use this skill when building, migrating, or reviewing integrations with UPS
shipping, rating, tracking, pickup, customs, delivery, forwarding, or supply
chain APIs.
Keep changes bounded to the documented API surface. Read the reference that
matches the integration task before changing request models, response models,
authentication, certificate handling, or error handling.
Reference index
| Reference |
Topics |
| Client migrations and compatibility |
Track Alert v2, consistent arrays, OAuth callbacks and Steppingstone, DigiCert, error codes |
| Shipping, rating, and shipment linkage |
Schema changes, surcharges, Premier, Windsor Lane, Roadie, Mexico tax IDs, World Ease, Worldwide Economy |
| Pickup and delivery |
Smart Pickup, Lab Logistics pickup points, protected delivery tokens, Delivery Intercept |
| International and supply chain |
Customs Detail, SCS ingestion, Forwarding, TradeDirect, Global Checkout, export and address assurance |
| Portal, webhooks, and agent integrations |
Central webhook credentials, portal MFA and onboarding, UPS MCP server |
Quick reference: breaking changes and migrations
Track Alert v2
- Version 2 of Track Alert and Track Alert with Photo removes the
destination object.
- Migrating clients must not require or deserialize
destination.
- Their events include
gmtOffset in (-/+)HH.MM form to explain local-time
conversion.
See
Client migrations and compatibility.
Consistent array response versions
Use v2403 when fields documented as arrays must consistently return arrays
for:
- Shipping
- Rating
- Pickup
- Dangerous Goods Chemical Reference Data
Use v2 for:
- Dangerous Goods Acceptance Audit Pre-check
- Pre Notification
- Paperless Documents
- Locator
- Quantum View
- Ship Void
- Address Validation
- Landed Cost
Older paths retain inconsistent scalar-or-array behavior for compatibility.
See
Client migrations and compatibility.
Removed and relaxed schema fields
LabelDelivery_EMail no longer has:
UndeliverableEMailAddress
FromEMailAddress
FromName
Memo
Subject
SubjectCode
Master_SoldTo.AttentionName is no longer required. Pickup creation makes
StateProvince optional.
See
Shipping, rating, and shipment linkage.
Newly required shipment inputs
- Roadie rating requests require
AddressLine.
- Mexico shipment requests require tax-ID information, matching the existing
requirement for Indonesia and Vietnam.
- Windsor Lane shipments require a commercial invoice or the API returns a
warning.
See
Shipping, rating, and shipment linkage.
OAuth and trust-store migration
- A localhost authorization-code callback must use
http:// and include a
port.
- Enter multiple callback URLs as a comma-separated list with no spaces.
- Steppingstone accepts existing SOAP/XML payloads while authentication moves
to OAuth 2.0.
- Clients connecting to
onlinetools.ups.com with a locally maintained trust
store must follow the DigiCert migration guidance and update that store.
See
Client migrations and compatibility
and
Client migrations and compatibility.
Quick reference: API and workflow additions
Pickup workflows
- The Smart Pickup API can trigger Smart Pickups independently of a
merchant's platform integration.
- The embeddable Smart Pickup Widget owns authentication, scheduling logic,
and UPS API communication.
- Pickup Notification Preferences manages notification settings at account
level.
- UPS Lab Logistics Pickup Points lets clinics and laboratories schedule daily
or date-specific Smart Pickups through a centralized API.
See
Pickup and delivery.
Delivery controls
- Protected Delivery Token tokenizes a shipper-generated PIN and lets the
shipper require that PIN before package release.
- Delivery Intercept automates intercept requests and provides an eligibility
endpoint for determining the valid intercept type before submission.
See
Pickup and delivery.
International checkout and compliance
- Customs Detail supplies current UPS-shipment compliance requirements before
customs data is submitted.
- Global Checkout is a GraphQL API for guaranteed international duty-and-tax
quotes at checkout.
- Export Assure provides interactive description-of-goods guidance and
destination-specific commodity compliance checks.
See
International and supply chain.
Freight and supply chain
- Forwarding creates and manages air, ocean, and ground freight-forwarding
shipments.
- SCS Inventory synchronizes WMS orders and updates for order and inventory
visibility; SCS Logistics ingests operational events in near real time; SCS
Transportation sends TMS shipments and updates to the UPS Supply Chain
Symphony datastore.
- TradeDirect supports direct international shipping from manufacturers to end
consumers, with shipment creation through the Shipping API.
See
International and supply chain.
Integration administration
- Manage Webhook Credentials centralizes webhook credential configuration and
maintenance.
- Accessing API credentials or an application in the Developer Portal prompts
reauthentication with MFA.
- The UPS MCP server exposes Track and Address Validation tools for agent
integrations.
See
Portal, webhooks, and agent integrations.
Task routing
Use the references as follows:
- For a client or authentication migration, start with
Client migrations and compatibility.
- For request or response model changes in Shipping or Rating, use
Shipping, rating, and shipment linkage.
- For pickup, release, intercept, or tracking behavior, use
Pickup and delivery.
- For customs, international checkout, freight, or supply chain ingestion,
use
International and supply chain.
- For portal access, webhooks, or agent tools, use
Portal, webhooks, and agent integrations.
1---2name: ups-shipping-knowledge-patch-23description: UPS Shipping4license: MIT5---678# UPS Shipping API Knowledge Patch910Use this skill when building, migrating, or reviewing integrations with UPS11shipping, rating, tracking, pickup, customs, delivery, forwarding, or supply12chain APIs.1314Keep changes bounded to the documented API surface. Read the reference that15matches the integration task before changing request models, response models,16authentication, certificate handling, or error handling.1718## Reference index1920| Reference | Topics |21| --- | --- |22| [Client migrations and compatibility](references/client-migrations-and-compatibility.md) | Track Alert v2, consistent arrays, OAuth callbacks and Steppingstone, DigiCert, error codes |23| [Shipping, rating, and shipment linkage](references/shipping-rating-and-linkage.md) | Schema changes, surcharges, Premier, Windsor Lane, Roadie, Mexico tax IDs, World Ease, Worldwide Economy |24| [Pickup and delivery](references/pickup-and-delivery.md) | Smart Pickup, Lab Logistics pickup points, protected delivery tokens, Delivery Intercept |25| [International and supply chain](references/international-and-supply-chain.md) | Customs Detail, SCS ingestion, Forwarding, TradeDirect, Global Checkout, export and address assurance |26| [Portal, webhooks, and agent integrations](references/portal-webhooks-and-agents.md) | Central webhook credentials, portal MFA and onboarding, UPS MCP server |2728## Quick reference: breaking changes and migrations2930### Track Alert v23132- Version 2 of Track Alert and Track Alert with Photo removes the33 `destination` object.34- Migrating clients must not require or deserialize `destination`.35- Their events include `gmtOffset` in `(-/+)HH.MM` form to explain local-time36 conversion.3738See39[Client migrations and compatibility](references/client-migrations-and-compatibility.md#track-alert-v2).4041### Consistent array response versions4243Use `v2403` when fields documented as arrays must consistently return arrays44for:4546- Shipping47- Rating48- Pickup49- Dangerous Goods Chemical Reference Data5051Use `v2` for:5253- Dangerous Goods Acceptance Audit Pre-check54- Pre Notification55- Paperless Documents56- Locator57- Quantum View58- Ship Void59- Address Validation60- Landed Cost6162Older paths retain inconsistent scalar-or-array behavior for compatibility.6364See65[Client migrations and compatibility](references/client-migrations-and-compatibility.md#consistent-array-responses).6667### Removed and relaxed schema fields6869`LabelDelivery_EMail` no longer has:7071- `UndeliverableEMailAddress`72- `FromEMailAddress`73- `FromName`74- `Memo`75- `Subject`76- `SubjectCode`7778`Master_SoldTo.AttentionName` is no longer required. Pickup creation makes79`StateProvince` optional.8081See82[Shipping, rating, and shipment linkage](references/shipping-rating-and-linkage.md#shipping-pickup-account-and-tracking-schema-changes).8384### Newly required shipment inputs8586- Roadie rating requests require `AddressLine`.87- Mexico shipment requests require tax-ID information, matching the existing88 requirement for Indonesia and Vietnam.89- Windsor Lane shipments require a commercial invoice or the API returns a90 warning.9192See93[Shipping, rating, and shipment linkage](references/shipping-rating-and-linkage.md#required-request-data).9495### OAuth and trust-store migration9697- A localhost authorization-code callback must use `http://` and include a98 port.99- Enter multiple callback URLs as a comma-separated list with no spaces.100- Steppingstone accepts existing SOAP/XML payloads while authentication moves101 to OAuth 2.0.102- Clients connecting to `onlinetools.ups.com` with a locally maintained trust103 store must follow the DigiCert migration guidance and update that store.104105See106[Client migrations and compatibility](references/client-migrations-and-compatibility.md#oauth-callback-registration)107and108[Client migrations and compatibility](references/client-migrations-and-compatibility.md#digicert-trust-store-migration).109110## Quick reference: API and workflow additions111112### Pickup workflows113114- The Smart Pickup API can trigger Smart Pickups independently of a115 merchant's platform integration.116- The embeddable Smart Pickup Widget owns authentication, scheduling logic,117 and UPS API communication.118- Pickup Notification Preferences manages notification settings at account119 level.120- UPS Lab Logistics Pickup Points lets clinics and laboratories schedule daily121 or date-specific Smart Pickups through a centralized API.122123See124[Pickup and delivery](references/pickup-and-delivery.md#smart-pickup-surfaces).125126### Delivery controls127128- Protected Delivery Token tokenizes a shipper-generated PIN and lets the129 shipper require that PIN before package release.130- Delivery Intercept automates intercept requests and provides an eligibility131 endpoint for determining the valid intercept type before submission.132133See134[Pickup and delivery](references/pickup-and-delivery.md#delivery-controls).135136### International checkout and compliance137138- Customs Detail supplies current UPS-shipment compliance requirements before139 customs data is submitted.140- Global Checkout is a GraphQL API for guaranteed international duty-and-tax141 quotes at checkout.142- Export Assure provides interactive description-of-goods guidance and143 destination-specific commodity compliance checks.144145See146[International and supply chain](references/international-and-supply-chain.md#customs-and-compliance).147148### Freight and supply chain149150- Forwarding creates and manages air, ocean, and ground freight-forwarding151 shipments.152- SCS Inventory synchronizes WMS orders and updates for order and inventory153 visibility; SCS Logistics ingests operational events in near real time; SCS154 Transportation sends TMS shipments and updates to the UPS Supply Chain155 Symphony datastore.156- TradeDirect supports direct international shipping from manufacturers to end157 consumers, with shipment creation through the Shipping API.158159See160[International and supply chain](references/international-and-supply-chain.md#freight-and-supply-chain-apis).161162### Integration administration163164- Manage Webhook Credentials centralizes webhook credential configuration and165 maintenance.166- Accessing API credentials or an application in the Developer Portal prompts167 reauthentication with MFA.168- The UPS MCP server exposes Track and Address Validation tools for agent169 integrations.170171See172[Portal, webhooks, and agent integrations](references/portal-webhooks-and-agents.md).173174## Task routing175176Use the references as follows:1771781. For a client or authentication migration, start with179 [Client migrations and compatibility](references/client-migrations-and-compatibility.md).1802. For request or response model changes in Shipping or Rating, use181 [Shipping, rating, and shipment linkage](references/shipping-rating-and-linkage.md).1823. For pickup, release, intercept, or tracking behavior, use183 [Pickup and delivery](references/pickup-and-delivery.md).1844. For customs, international checkout, freight, or supply chain ingestion,185 use186 [International and supply chain](references/international-and-supply-chain.md).1875. For portal access, webhooks, or agent tools, use188 [Portal, webhooks, and agent integrations](references/portal-webhooks-and-agents.md).