Skip to main content
Technical Preview

Overview

Client-mode REST API connector for the UPS Developer Portal APIs: OAuth 2.0 client credentials, package tracking, Track Alert push subscriptions, rating and shop rates, address validation, time in transit, locations and Access Points, shipments and labels (purchase), void, label recovery, landed cost, pickups (purchase), paperless trade documents, Quantum View, Delivery Intercept eligibility and charges, dangerous goods data; companion server connector for Track Alert webhooks. This is one of the templates in the UPS Developer Portal REST API app (ups-developer-portal). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No UPS developer app (client id / secret) or shipper account on the factory box (no UPS_* variables); only static, mock, negative-control and unauthenticated / fake-credential public probes ran.

Auth

OAuth 2.0 client credentials (client_secret_basic): GetToken posts grant_type=client_credentials (form) to /security/v1/oauth/token with Authorization: Basic base64(client_id:client_secret); GetTokenForAccount adds x-merchant-id (shipper account). Reply access_token, token_type, issued_at, expires_in (seconds, string), status; no refresh token. UpsApi events: Authorization: Bearer <access_token>, transId <unique, max 32> and transactionSrc Coreflux-Broker. Every event also sends User-Agent: Coreflux-Broker. Auth headers used by the template: Authorization: Bearer {value.json.access_token}.

Template parameters

BASE_ADDRESS default: https://onlinetools.ups.com.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call TrackPackage by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026