Get Tracking

Return the complete tracking history of a shipment, in chronological order.

GET /tracking/{ldv}

Request

Headers

Header	Value
`Authorization`	`Bearer <access_token>`
`Accept`	`application/json`

Path Parameters

Parameter	Type	Required	Description
`ldv`	`string`	Yes	Shipment number. Exactly 12 characters, case-insensitive

Shipments are searchable for 90 days after creation. Older shipments return 404.

Example

cURL


curl https://delivery.spedisci.online/api/v2026-04/tracking/ABC123456789 \
  -H "Authorization: Bearer <access_token>" \
  -H "Accept: application/json"

Response Fields

Field	Type	Description
`tracking_number`	`string`	The shipment number, uppercased
`events`	`Event[]`	Tracking events, oldest first

Event Object

Field	Type	Description
`code`	`number \| string`	Internal tracking event code. Empty string `""` when the description has no mapped code
`date`	`string`	ISO-8601 timestamp of the event
`description`	`string`	Human readable event description (Italian)
`place`	`string \| null`	Where the event happened. Falls back to the depot city of the operator; when the event has notes they are appended in parentheses

description is the authoritative label of an event. code is a stable internal identifier that may be absent for less common descriptions — do not rely on it being present.

Response Codes

Code	Description
`200`	OK — tracking object returned
`204`	No Content — the shipment exists but has no tracking events yet
`400`	The shipment number is not valid (not 12 characters)
`401`	Missing or invalid access token
`404`	Shipment not found within the 90-day lookup window

Error Examples


{
  "code": 400,
  "status": "error",
  "message": "Shipment number not valid!"
}


{
  "code": 404,
  "status": "error",
  "message": "Shipment not found!"
}

A 204 No Content response has an empty body by HTTP definition. Treat it as “the shipment is known but nothing has happened to it yet”, not as an error.

Polling vs Webhooks

Polling this endpoint is fine for one-off lookups, but for continuous monitoring use webhook notifications instead — you receive an update the moment the status changes, and the notification payload embeds this exact same tracking object.