Tracking, in your application.
Retrieve a demo shipment’s current status and visible timeline as JSON. Every response explicitly identifies simulated data.
/api/v1/tracking/{number}
Send your API key in the Authorization header from your server. Keep it out of browser code and public repositories.
curl "https://4px.it.com/api/v1/tracking/DEMO4PX10000001" \ -H "Authorization: Bearer YOUR_API_KEY"
During deployment, replace the domain above with your Vercel preview URL.
Example response (abbreviated)
{
"number": "DEMO4PX10000001",
"simulated": true,
"notice": "Demo shipment. All events are simulated, not carrier scans.",
"destination": "San Martin, United States",
"carrier": "GOFO",
"estimatedDelivery": "2025-10-07T22:17:00.000Z",
"status": "Delivered (simulated)",
"events": [
{
"at": "2025-10-07T22:17:00.000Z",
"location": "San Martin",
"description": "Delivered to door / yard (simulated)",
"stage": 5,
"simulated": true
}
]
}Predictable responses
200 Shipment found
400 Invalid tracking number
401 Invalid or missing API key
404 Shipment not found
429 Rate limit reached
503 Service unavailable
Privacy by default
Responses include city, country, carrier, and events. Customer names, emails, and street addresses are never included.
Time-aware events
Dates use ISO 8601 in UTC. Only events whose scheduled time has passed appear. The estimatedDelivery field exposes the estimated delivery timestamp. Dispatch schedule, transit duration, future events, and next-update timestamps remain admin-only. Up to 120 API requests per minute per IP address.