Carriers
Pos Malaysia (Pos Laju) Tracking API & MCP
Query live Pos Malaysia (posmalaysia) package status and scan history in a single synchronous GET request or MCP tool call. lastscanned auto-detects UPU S10 numbers ending MY (with a valid check digit) in Pass 1 and returns a normalized TrackingResult JSON payload, with no Pos Malaysia account or API key.
Overview & Quick Facts
| Property | Value |
|---|---|
Carrier slug (?carrier=) | posmalaysia |
| Brand & service aliases | Pos Malaysia, Pos Laju, Poslaju, pos.com.my, S10 …MY |
| Category | National postal operator (Malaysia), domestic and international parcels and mail |
| Single-package REST endpoint | GET https://api.lastscanned.com/v1/track/{trackingNumber} |
| Batch REST endpoint | GET https://api.lastscanned.com/v1/track?numbers=EN123456785MY,... |
MCP server (https://mcp.lastscanned.com) | track_package, track_packages, list_carriers (claude mcp add --transport http lastscanned https://mcp.lastscanned.com) |
| Authentication & pricing | Authorization: Bearer lsk_live_... · 1 free keyless lookup/day per IP · Free tier (5 unique numbers/day, $0) · Pro ($4.99/mo for 1,000 unique numbers, unlimited re-polls, $0.015/extra) · HTTP 402 Stripe MPP ($0.50 for 25-number lsk_pack_ key or $0.02/number in USDC on Tempo) |
Tracking Number Formats & Auto-Detection
| Pass | Rule | Check digit | Examples |
|---|---|---|---|
Pass 1 (matches) | UPU S10: two letters, nine digits, MY | Yes (S10) | EN123456785MY |
Pass 2 (mayMatch) | None | n/a | n/a |
Local Pos Laju numbers that are not S10 shaped can be tracked with ?carrier=posmalaysia.
Synchronous GET Request & Normalized JSON Response
curl
curl -s "https://api.lastscanned.com/v1/track/EN123456785MY" \
-H "Authorization: Bearer $LASTSCANNED_API_KEY"JavaScript / TypeScript (fetch)
const res = await fetch("https://api.lastscanned.com/v1/track/EN123456785MY", {
headers: { Authorization: `Bearer ${process.env.LASTSCANNED_API_KEY}` },
});
const pkg = await res.json();
console.log(pkg.status, pkg.events[0]);MCP track_package tool call
{
"tool": "track_package",
"arguments": {
"tracking_number": "EN123456785MY"
}
}Normalized TrackingResult JSON response
{
"carrier": "posmalaysia",
"trackingNumber": "EN123456785MY",
"status": "out_for_delivery",
"statusDescription": "Your parcel is with our courier and is out for delivery",
"service": null,
"deliveredAt": null,
"deliveredAtLocal": null,
"signedBy": null,
"destination": {
"city": "Kuala Lumpur",
"state": "Kuala Lumpur",
"country": "MY"
},
"events": [
{
"timestamp": "2026-10-26T01:52:32Z",
"localTime": "2026-10-26T09:52:32",
"status": "out_for_delivery",
"description": "Your parcel is with our courier and is out for delivery",
"location": "Pusat POS Laju Kepong",
"code": "EM014"
},
{
"timestamp": "2026-10-25T19:16:01Z",
"localTime": "2026-10-26T03:16:01",
"status": "in_transit",
"description": "Your parcel has been sorted. We are on our way!",
"location": "HUB Parcel Domestik Shah Alam",
"code": "EM010"
},
{
"timestamp": "2026-10-24T02:05:10Z",
"localTime": "2026-10-24T10:05:10",
"status": "in_transit",
"description": "We have received your parcel and can't wait to deliver it!",
"location": "POS Laju Kiosk",
"code": "EM001"
}
]
}Notes
- Scan times are Malaysia time, returned with a UTC
timestampand the scan'slocalTime. destinationcomes from the recipient's city, state and country that Pos Malaysia reports.- The tracking page asks for a phone number only before showing the proof-of-delivery photo. The scans do not need it, and
lastscanneddoes not return the photo. - Up to 5 numbers go in one batch request.
Related Resources
- Carrier hub: All supported carriers
- Regex & check digits: Tracking number formats & auto-detection
- AI support workflows: WISMO AI agents & synchronous tracking
KEX Express Thailand (Kerry Express) Tracking API & MCP
Track KEX Express Thailand (formerly Kerry Express Thailand) parcels via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.
GDEX (Malaysia) Tracking API & MCP
Track GDEX Malaysia consignments via synchronous REST GET or MCP. Normalized JSON status and scan history, no carrier credentials required.