Aramex Tracking API & MCP
Query live Aramex (aramex) package status and scan history in a single synchronous GET request or MCP tool call. Aramex numbers are 10 or 11 digits, shapes that GLS Europe and DHL Express also use, so pass ?carrier=aramex. Aramex Australia/NZ (aramexau) is a separate carrier.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | aramex |
| Brand aliases | Aramex, Aramex International, Aramex Shop & Ship |
| Category | International express and e-commerce |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber}?carrier=aramex |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=51234567890,9876543210&carrier=aramex |
MCP server (https://mcp.lastscanned.com) | track_package, track_packages, list_carriers |
| Authentication & pricing | Authorization: Bearer lsk_live_... · 1 free keyless lookup/day per IP |
Tracking Number Formats & Auto-Detection
| Pass | Rule / Regex | Check Digit | Examples |
|---|---|---|---|
Pass 1 (matches) | none | none | none |
Pass 2 (mayMatch) | none | none | none |
Aramex's 11-digit numbers carry a mod-7 check digit (the first ten digits mod 7 equal the last digit) and its Express and Shop & Ship numbers have 10 digits, but GLS Europe (11 digits) and DHL Express (10 digits) use the same shapes. Always pass ?carrier=aramex.
Synchronous GET Request & Normalized JSON Response
curl -s "https://api.lastscanned.com/v1/track/51234567890?carrier=aramex" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"{
"carrier": "aramex",
"trackingNumber": "51234567890",
"status": "delivered",
"statusDescription": "The shipment has been delivered",
"service": "E-commerce Parcel Express",
"deliveredAt": null,
"deliveredAtLocal": "2026-10-15T20:28:00",
"signedBy": null,
"destination": { "city": "Sharjah", "state": null, "country": "United Arab Emirates" },
"message": null,
"events": [
{
"timestamp": null,
"localTime": "2026-10-15T20:28:00",
"status": "delivered",
"description": "The shipment has been delivered",
"location": "Umm Ramool, United Arab Emirates",
"code": null
},
{
"timestamp": null,
"localTime": "2026-10-14T16:17:00",
"status": "label_created",
"description": "Shipper generated a new shipment label, but the shipment has not been handed over to Aramex, yet. Shipment will be updated once collected from shipper and received in Aramex offices",
"location": "Dubai, United Arab Emirates",
"code": null
}
]
}Notes
- Time zone: scan times are the local clock of the place named, with no zone, so only
localTimeis set andtimestampisnull. - Handoff: when a scan reads "Shipment forwarded by UPS under tracking number ...",
messagenames that carrier and number (for example"Handed to UPS as 1Z999AA10123456784"). Pass the number toGET /v1/track/{number}for its own scans. - Network-wide scans: scans labelled "Aramex Update" or "Network Update" have no place, so
locationisnull. - Destination:
countryis the full English name, as Aramex prints it. - Not found: an unknown number returns
not_found.
Related Resources
- Regex & check digits: Tracking number formats & auto-detection
Sagawa Express Tracking API & MCP
Track Sagawa Express (佐川急便, Japan) parcels by waybill number via synchronous REST GET or MCP. Normalized JSON with the current delivery state, no carrier credentials required.
T-cat (Taiwan Pelican Express) Tracking API & MCP
Track T-cat (Taiwan Pelican Express) parcels with one synchronous REST GET or MCP call. Normalized JSON status and scan history, no carrier credentials required.