Tracking
One endpoint for parcel tracking. Pass a tracking number, get normalised scan events back — no carrier slug, no account setup.
Pass the tracking number as num (alias id). Events come back newest-first; each carries a status, a date and hour, and where it was last seen (location, country).
GET/v1/tracking
Parameters
numreqstringThe tracking number to look up (alias: id).
Example
request
curl "https://repsapi.com/v1/tracking?num=YT2530998211074512" \
-H "Authorization: Bearer YOUR_KEY"200 · response
{
"tracking_number": "YT2530998211074512",
"count": 2,
"updates": [
{
"date": "2026-06-21",
"hour": "08:14",
"status": "Departed facility",
"location": "Shenzhen",
"country": "CN"
},
{
"date": "2026-06-19",
"hour": "22:01",
"status": "Accepted by carrier",
"location": "Shenzhen",
"country": "CN"
}
],
"source": "repsapi.com",
"attribution": "Data provided by repsapi.com — free reps API",
"docs": "https://repsapi.com/docs"
}Update fields
status— the scan event text (e.g. "Departed facility").date— event date,YYYY-MM-DD.hour— event time,HH:MM.location— city/facility where it was scanned.country— ISO country code, ornullif unknown.
When the number isn't recognised yet the API returns 200 with an empty updates array (count: 0) rather than an error.