Skip to Content

Developer / API Learning Center

Integrate shipping, tracking, labels, and rate quotes into your platform.

New Account Explore Our Services

Track shipments

Use our tracking endpoint to get real-time shipment status. Results may include driver GPS (when available), reference, signature, event history, and timing details.

No API key is required for tracking. However, for privacy and security, if you don’t include a key we may return approximate locations (for example, using the center of the ZIP code) instead of exact pickup/delivery coordinates.
Open API Explorer Download OpenAPI YAML

Endpoint

GET https://www.jetdelivery.com/api/v1/utilities/track/

Quick examples

# Simplest form (no key required)
curl "https://www.jetdelivery.com/api/v1/utilities/track/?idx=2345678"

# Treat id as a billing reference instead of a tracking number
curl "https://www.jetdelivery.com/api/v1/utilities/track/?idx=ABC123&ref=link-ref"

# Include key to unlock account-authorized details (recommended)
curl "https://www.jetdelivery.com/api/v1/utilities/track/?idx=2345678&key=YOUR_API_KEY"

Tip: If you’re calling from a browser, you can paste the URL directly. For production integrations, call server-side.

Parameters

Click any parameter to expand details.

idx string Required
Shipment identifier. This can be:
  • a 6–8 digit tracking number (example: 2345678), or
  • a billing/reference value (up to 23 characters) when used with ref=link-ref.
ref string Optional
If set to link-ref, Jet will attempt to match id to a billing reference in our system rather than a tracking number.
key string Optional
Your API key (linked to a Jet Delivery account). Not required for tracking, but recommended to return account-authorized details (including more precise location data where applicable).

Response

Responses include the shipment’s latest status and a timeline of events. Some fields may be null depending on the shipment state (for example, GPS may be unavailable after delivery).

Example (in transit with GPS)

{
  "error": null,
  "data": {
    "track_no": "3766585",
    "status_code": "10",
    "status_description": "Picked-up",
    "status_datetime": "2026-02-28T09:28:00-08:00",
    "driver_no": "222",
    "active_jobs_on_driver": 14,
    "geolocation": "33.97108035569377,-117.55337365945977",
    "geolocation_is_actual": "true",
    "origin_geolocation": "34.09507300,-117.77093590",
    "destination_geolocation": "34.09507300,-117.77093590",
    "reference": "LEAF IGNORE",
    "events": [
      { "datetime": "2026-02-28T09:28:55-08:00", "description": "Driver dispatched to La Verne, CA 91750" },
      { "datetime": "2026-02-28T09:28:00-08:00", "description": "Driver departed from La Verne, CA 91750" }
    ]
  }
}

GPS fields may be null when a driver is not actively tracking, when GPS is unavailable, or after delivery.

Example (delivered with signature)

{
  "error": null,
  "data": {
    "track_no": "3765352",
    "status_code": "15",
    "status_description": "Delivered",
    "status_datetime": "2026-02-26T13:09:00-08:00",
    "driver_no": "610",
    "reference": "24528",
    "signature": "Susana Mendoza",
    "more_details_uri": "/smartship/tools/order/?idx=3765352",
    "events": [
      { "datetime": "2026-02-25T17:10:00-08:00", "description": "Order scheduled via telephone" },
      { "datetime": "2026-02-26T11:44:47-08:00", "description": "Driver dispatched to Los Angeles, CA 90048" },
      { "datetime": "2026-02-26T13:09:00-08:00", "description": "Drop-off completed in Brentwood, CA 90049" }
    ]
  }
}
Note: The events array may be newest-to-oldest or oldest-to-newest depending on shipment type and history. If ordering matters for your UI, sort by datetime.

Next steps