UniUni Tracking API for Developers

Use C2W Package Tracking API to retrieve UniUni shipment information through RapidAPI. The documented endpoint accepts a tracking number and returns JSON for your application. Webhooks are not supported.

How to request UniUni tracking

Subscribe on RapidAPI and keep your credentials on your server.
Send your shipment’s tracking number as trackingNumber to GET /TrackingPackage.
Check the HTTP response before reading tracking fields. Use the API reference for headers and schema.

curl --get 'https://trackingpackage.p.rapidapi.com/TrackingPackage' \
  --data-urlencode 'trackingNumber=YOUR_TRACKING_NUMBER' \
  --header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY' \
  --header 'X-RapidAPI-Host: trackingpackage.p.rapidapi.com'

Add an Authorization header only if it was issued for your integration. This example uses a placeholder; it does not query a real shipment.

Illustrative response, not a live shipment

This synthetic subset illustrates documented field names. It is not a recorded UniUni response or a guarantee that every shipment supplies these values.

{
  "TrackingNumber": "YOUR_TRACKING_NUMBER",
  "Carrier": "UniUni",
  "Delivered": false,
  "Status": "In transit"
}

See authentication and error handling. Keep credentials server-side and treat network failures separately from shipment status.

Plan polling and cost before subscribing

Webhooks are not supported. Your application schedules requests and customer notifications. Results may be cached; a successful call does not imply a new carrier scan.

Example: 25 active shipments checked four times per day use 100 requests, before retries and manual refreshes. The Pro plan includes 150 requests/day at $9.99/month, leaving 50 requests of headroom. This is a workload example, not a recommended polling interval.

The free plan includes 5 requests/day for evaluation. Space requests within the rate limit and stop routine polling when your workflow is complete. Compare plans and request budgets; confirm applicable terms in RapidAPI.

Evaluate your UniUni delivery workflows.

Test shipments from the regions and services you use rather than assuming every route provides identical fields. Keep tracking numbers as strings and preserve scan wording for customer support. Compare available event times without inventing a timezone or a new scan for each poll.

Read our alternative last-mile carrier overview for carrier-reported network context. Coverage and C2W field availability must be evaluated separately.

Fields to consider in your application

Integration considerations, not guaranteed field availability
Field	Application handling
`Status`	Preserve the returned status text.
`Delivered`	Do not infer delivery from missing data.
`TrackingDetails`	Handle absent or empty event history.

Available values depend on the shipment and carrier data. Empty strings, null values, and absent fields should not break your interface. These are schema notes, not a recorded UniUni production response.

Before going live

Test delivered, in-transit, unavailable-data, and exception cases for your services. Establish your polling schedule, request headroom, and support process. Use our integration guide and request-budget examples.