Multi-Carrier Package Tracking (USPS, UPS, FedEx)
Pricing
from $0.01 / 1,000 results
Multi-Carrier Package Tracking (USPS, UPS, FedEx)
Track Packages Across All Major Carriers Managing shipments from multiple carriers is a pain. Different APIs, different authentication methods, different response formats. USPS uses XML, UPS requires OAuth, FedEx has its own auth flow. The Multi-Carrier Package Tracking tracks all
Pricing
from $0.01 / 1,000 results
Rating
5.0
(1)
Developer
The Howlers
Maintained by CommunityActor stats
0
Bookmarked
68
Total users
8
Monthly active users
5 days ago
Last modified
Categories
Security
Limited permissionsShare
Track packages across USPS, UPS, and FedEx with a single API call. Auto-detects carrier from tracking number format.
BYOK (Bring Your Own Key) -- you provide your own API credentials.
Before You Start
This actor requires your own API credentials to fetch real data.
Where to get your key: Your USPS Web Tools API User ID. Get one free at https://www.usps.com/business/web-tools-apis/
You can test with Demo Mode first (free, no key needed) to see the output format before committing.
Quick Start
Test with Demo Mode (free, no API key needed)
{"demoMode": true,"trackingNumbers": ["1Z999AA10123456784","9400111899223456789012","794644790138"]}
Run with real data
{"demoMode": false,"trackingNumbers": ["1Z999AA10123456784","9400111899223456789012","794644790138"],"uspsUserId": "YOUR_API_KEY_HERE","upsClientId": "YOUR_API_KEY_HERE","upsClientSecret": "YOUR_API_KEY_HERE","fedexApiKey": "YOUR_API_KEY_HERE","fedexSecretKey": "YOUR_API_KEY_HERE","fedexAccountNumber": "YOUR_API_KEY_HERE"}
Input Parameters
| Parameter | Type | Default | Required | Description |
|---|---|---|---|---|
trackingNumbers | array | - | Yes* | List of tracking numbers to look up (one per line or comma-separated). Carrier is auto-detected from the format. |
demoMode | boolean | false | No | Run with sample data without API credentials. Perfect for testing integrations. |
uspsUserId | string | - | Yes* | Your USPS Web Tools API User ID. Get one free at https://www.usps.com/business/web-tools-apis/ |
upsClientId | string | - | Yes* | Your UPS API Client ID from developer.ups.com |
upsClientSecret | string | - | Yes* | Your UPS API Client Secret |
fedexApiKey | string | - | Yes* | Your FedEx Developer API Key from developer.fedex.com |
fedexSecretKey | string | - | Yes* | Your FedEx Developer Secret Key |
fedexAccountNumber | string | - | Yes* | Your FedEx Account Number (optional, for some endpoints) |
*Required when Demo Mode is off.
Pricing
This actor uses pay-per-event billing:
| Event | When it is charged | Price |
|---|---|---|
| Actor start | Once when the run starts, one event per GB of memory (minimum one). At the default 4 GB of memory a run starts at $0.0002 | $0.00005 per GB |
| Package Tracking Lookup | Track a single package across USPS, UPS, or FedEx | $0.005 |
| Result | Each item written to the default dataset | $0.00001 |
Demo mode is free -- no charges for sample data.
Troubleshooting
"API key is required"
You have Demo Mode turned off but didn't provide an API key. Either:
- Turn Demo Mode on to test with sample data
- Add your API key in the input
"API error 403" or "Unauthorized"
Your API key is invalid, expired, or doesn't have access to this specific API endpoint. Double-check your key and account permissions.
"API error 429" or "Rate limit"
Too many requests. Wait a minute and try again, or reduce the number of items per run.
No results or empty dataset
Check the run log for error messages. Common causes:
- Invalid input format (check the examples above)
- API key without proper permissions
- The target data doesn't exist or is too small to track
How do I test without an API key?
Enable Demo Mode in the input. This returns realistic sample data so you can verify the output format works for your workflow.
Built by John Rippy | Actor Arsenal