Get Delivery Status

DashLink provides two different tracking endpoints, each serving a different purpose:

1. Unauthenticated tracking history
2. Authenticated Drive delivery status

---

Endpoint #1 — Unauthenticated event history (recommended for tracking)

GET /webhooks/drive/geteventhistory/{external_delivery_id}

Use cases:

• Retrieve the full event history
• Build customer tracking pages
• QA and debugging
• Map webhook-based states

This endpoint returns all parcel lifecycle events such as:

• parcel_labeled
• parcel_scanned
• parcel_mid_mile_arrived
• dasher_picked_up
• dasher_dropped_off
• Redelivery and failure events

Returned data includes:

• event_name
• Timestamp
• Location (city, state, ZIP)
• Sequence of events

Example response:

{
  "eventHistory": [
    { "event_name": "parcel_labeled", "timestamp": "2024-06-24T23:43:44Z" },
    { "event_name": "arrived_at_mid_mile_facility", "timestamp": "2024-06-25T03:45:48Z" },
    { "event_name": "departed_mid_mile_facility", "timestamp": "2024-06-25T03:56:50Z" },
    { "event_name": "parcel_scanned", "timestamp": "2024-06-25T12:55:21Z" },
    { "event_name": "dasher_picked_up", "timestamp": "2024-06-25T18:22:36Z" },
    { "event_name": "dasher_attempted_delivery", "timestamp": "2024-06-25T18:58:23Z" },
    { "event_name": "parcel_received_to_redeliver", "timestamp": "2024-06-25T22:05:14Z" },
    { "event_name": "dasher_picked_up", "timestamp": "2024-06-26T18:33:28Z" },
    { "event_name": "dasher_confirmed_dropoff_arrival", "timestamp": "2024-06-26T19:01:21Z" },
    { "event_name": "dasher_dropped_off", "timestamp": "2024-06-26T19:02:02Z" }
  ]
}

---

Endpoint #2 — Authenticated Drive delivery status

GET /drive/v2/deliveries/{external_delivery_id}

See the Drive API Reference for the full schema.

Use cases:

• Fetch current delivery metadata
• Access POD images (dropoff photo, signature)
• Retrieve dasher vehicle details
• Get updated delivery time estimates

This endpoint is not recommended for building tracking timelines because:

• It returns only the current status, not the full history
• Its status codes are tailored toward same-day restaurant deliveries
• Status Codes Returned:
  • quote
  • created
  • confirmed
  • enroute_to_pickup
  • arrived_at_pickup
  • picked_up
  • enroute_to_dropoff
  • arrived_at_dropoff
  • delivered
  • enroute_to_return
  • arrived_at_return
  • returned
  • cancelled

---

Recommended usage pattern

Need	Endpoint
Full history	geteventhistory
Customer-facing tracking	geteventhistory
Proof of delivery image	Authenticated status endpoint
Dasher location / vehicle details	Authenticated status endpoint
Troubleshooting	Both

---

Why webhooks + history endpoint are preferred

• Webhooks deliver events in real time
• The history endpoint allows you to backfill or re-sync state
• Combined, they provide the most complete view of a parcel lifecycle

---