Scope
The public endpoint supports one operation: looking up a ZIM booking, bill of lading, or container reference. It does not create a booking, provide a shipping quote, expose carrier credentials, or guarantee that a carrier update is available. Start with the JSON discovery document or OpenAPI 3.1 contract. Quote and operational requests require human review through the contact page.
Endpoint
GET https://adi-shipping.com/api/v1/tracking.php?reference=REFERENCE
The reference query parameter is required. It may contain letters, digits, dots, underscores, slashes, and hyphens, with a maximum length of 40 characters. The endpoint needs no client API key and is rate-limited to protect carrier capacity and customer privacy.
Quickstart
curl --get 'https://adi-shipping.com/api/v1/tracking.php' \
--data-urlencode 'reference=YOUR_REFERENCE' \
--header 'Accept: application/json'The RateLimit-Policy and RateLimit response headers describe the allowance and remaining requests. Compatibility fields RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset are also returned. A 429 response includes Retry-After.
Responses and recovery
Successful responses contain ok: true and a tracking object with carrier, vessel, status, location, ETA, and event fields. Errors use application/problem+json, the RFC 9457 members, a stable code, and a resolution hint. Read the complete typed error model.
Contract and responsible use
Use the official Adi Shipping CLI, read the versioning and deprecation policy, and inspect the machine-readable OpenAPI specification. Do not enumerate references, store shipment details longer than needed, or present estimated arrival information as guaranteed. There is no API key, registration process, or sandbox.
The compatibility alias /api/tracking.php is deprecated from 10 October 2026, sunsets on 1 April 2027, and advertises the v1 successor and policy through HTTP headers.