Bulk Operations

If you're checking on more than a handful of orders at once — end-of-day reconciliation, a support queue, or syncing status into your own system — these batch endpoints save you from looping over single-order calls.

Bulk Tracking

Track up to 50 AWBs in a single call. Same per-order shape as single tracking, returned as a list.

Code
curl -X POST https://dale.staging.shadowfax.in/api/v4/clients/bulk_track/ \
  -H "Authorization: Token your_api_token" \
  -H "Content-Type: application/json" \
  -d '{"awb_numbers": ["SF1234567890", "SF1234567891"]}'

Code
{
  "message": "Success",
  "data": [
    {
      "order_details": { "awb_number": "SF1234567890", "status": "recd_at_fwd_hub", "status_display": "Received At Forward Hub", "..." : "..." },
      "tracking_details": [ "..." ]
    },
    {
      "order_details": { "awb_number": "SF1234567891", "status": "delivered", "status_display": "Delivered to customer", "..." : "..." },
      "tracking_details": [ "..." ]
    }
  ]
}

Requests over the 50-AWB limit return a 400 with "Number of AWBs exceeded. Max count allowed is 50".

See Bulk Track in the API Reference.

Polling vs Webhooks

Prefer webhooks for real-time updates. Use bulk tracking as a daily reconciliation mechanism to catch any callbacks your system may have missed, not as your primary status source.

Bulk POD (Proof of Delivery)

Fetch recipient/proof-of-delivery details for up to 100 completed orders in one call — useful for batch-closing a settlement cycle or answering a backlog of delivery-confirmation queries at once. For a single order, see Label & POD.

Code
curl -X POST https://dale.staging.shadowfax.in/api/v1/clients/pod_details/ \
  -H "Authorization: Token your_api_token" \
  -H "Content-Type: application/json" \
  -d '{"awb_numbers": ["SF1234567890", "SF1234567891"]}'

Code
{
  "message": "Success",
  "pod_details": {
    "SF1234567890": {
      "recipient": "Customer",
      "recipient_name": "Rahul Sharma",
      "recipient_contact": "9876543210",
      "recipient_signature": []
    },
    "SF1234567891": {}
  }
}

POD details are only populated for orders in delivered, rts_d, or rto_d status — see Order Lifecycle. Orders outside those statuses (or older than ~6 months) return an empty object for that AWB rather than an error.

See Fetch POD Details in the API Reference.