Should I use this guide or the Shiprocket guide?

Use this guide if you have a direct Delhivery merchant account and ship through Delhivery directly. Use the Shiprocket guide if you use Shiprocket to manage your shipping across multiple couriers including Delhivery. Shiprocket normalises events from all courier partners into one webhook format, which is simpler if you use multiple couriers.

What authentication does Delhivery use?

Delhivery uses a token-based authentication. The API token is obtained from your Delhivery Merchant Portal. Pass it in the Authorization header as Token YOUR_TOKEN (not Bearer). For the push webhook, Delhivery posts to your endpoint; you configure any authorization header you want Delhivery to include, such as a secret header that WA.Expert verifies.

Why is the WhatsApp not sending after the webhook fires?

The most common reason is the phone number format. Delhivery sends the phone field as a bare 10-digit number such as 9876543210 without the country code. WA.Expert requires +919876543210. Prepend +91 in the automation mapping before sending.

What are the Delhivery tracking status codes?

Key Delhivery status codes for WhatsApp notifications: OFD (Out for Delivery), DL (Delivered), UD (Undelivered, triggers NDR WhatsApp), PKD or Manifested (Dispatched). The status field in the webhook payload gives the full text while status_code gives the short code. Branch your automation on status_code for reliability.

What if the phone number is missing from the Delhivery webhook?

Delhivery includes the consignee phone in the webhook only if it was provided when the shipment was created. Ensure your order management system passes the customer phone when creating Delhivery shipments via API. If the phone is missing, WA.Expert can perform a secondary lookup in your order database using the waybill number to find the customer's WhatsApp number.

Does this work with Delhivery reverse logistics?

Yes. The tracking status codes and webhook format are the same across Delhivery Express, Surface, and Reverse logistics. The same WA.Expert integration handles all three service types.

Connect Delhivery to WhatsApp — Tracking Alerts

Using Shiprocket? Use the Shiprocket guide instead

This guide is for brands with a direct Delhivery merchant account. If you ship through Shiprocket (which uses multiple couriers including Delhivery), use the Shiprocket integration guide instead. Shiprocket normalises events from all couriers into one webhook format.

Delhivery sends bare 10-digit numbers: always prepend +91

The phone field in Delhivery's webhook payload is a bare 10-digit number such as 9876543210. WA.Expert requires +919876543210. Prepend +91 in your automation before mapping to the WhatsApp destination.

Two integration options

Option	How it works	Best for
A: Webhook push (recommended)	Delhivery POSTs to your WA.Expert URL on every status change. Real-time.	Direct Delhivery accounts with API access.
B: Polling API	WA.Expert calls Delhivery's tracking API at intervals to check AWB status.	Accounts without webhook access, or for on-demand WISMO lookups.

Option A: Webhook push (recommended)

Step 1: Get your WA.Expert webhook URL

In WA.Expert, create a new automation with an Inbound Webhook trigger. Copy the webhook URL.

Step 2: Register in Delhivery Merchant Portal

Go to Settings → API → Webhooks.

Add your WA.Expert webhook URL as the push endpoint for tracking status updates.

Optionally, add an authorization header Delhivery should include in the POST (e.g. X-Secret: your-secret-value) so you can verify requests in WA.Expert.

Official docs

Delhivery API: delhivery-express-api-doc.readme.io

Step 3: Understand the webhook payload

Delhivery webhook payload — out for delivery

{{
  "waybill":     "1610000000001",
  "status":      "Out for Delivery",
  "status_code": "OFD",
  "remarks":     "Shipment out for delivery",
  "timestamp":   "2026-06-24T09:30:00Z",
  "phone":       "9876543210",
  "consignee":   "Priya Sharma"
}}

Map to WA.Expert variables:
  consignee   -> customer_name
  '+91' + phone -> wa_phone    <- PREPEND +91
  waybill     -> awb
  status      -> shipment_status
  status_code -> status_code   (use for branching)
  timestamp   -> event_time

Delhivery status codes and which WhatsApp to send

status_code	Full status	WhatsApp to send
PKD / Manifested	Picked up / Dispatched	Dispatch notification with waybill, expected delivery, tracking link.
OFD	Out for Delivery	OFD alert: 'Your order is out for delivery today. Please be available.'
DL	Delivered	Delivery confirmation + review request.
UD	Undelivered (NDR)	NDR rescheduling prompt within 60 minutes of the event.
RTO	Return to Origin	RTO notification: 'Your shipment is being returned. Contact us to rearrange.'

Branch your WA.Expert automation on status_code for reliable routing. Use status (full text) only as a display value in the message.

Option B: Polling the tracking API

If webhook push is not available on your Delhivery account, or if a customer asks for tracking status on WhatsApp, use the tracking API directly.

Delhivery tracking API call via WA.Expert External API Request step

GET https://track.delhivery.com/api/v1/packages/json/?token=YOUR_TOKEN&waybill={{awb}}&verbose=2
Authorization: Token YOUR_DELHIVERY_TOKEN

Response (simplified):
{{
  "ShipmentData": [
    {{
      "Shipment": {{
        "AWB":    "1610000000001",
        "Status": {{"Status": "Delivered", "StatusCode": "DL"}},
        "Consignee": {{"Name": "Priya Sharma", "MobileNo": "9876543210"}}
      }}
    }}
  ]
}}

Map:
  ShipmentData[0].Shipment.Status.Status     -> status_text
  ShipmentData[0].Shipment.Status.StatusCode -> status_code
  ShipmentData[0].Shipment.Consignee.Name    -> consignee_name

Token from: Delhivery Merchant Portal → Settings → API → Generate Token
Token format: pass as query param (?token=TOKEN) AND in Authorization header.

Token auth format for Delhivery API

Delhivery uses Token not Bearer. The Authorization header must be: Authorization: Token YOUR_TOKEN. Also pass the token as a query parameter: ?token=YOUR_TOKEN. Both are needed for the tracking API.

Worked example: OFD and NDR WhatsApp automation

Automation — Delhivery webhook to WhatsApp

1. Delhivery fires OFD webhook to WA.Expert:
   waybill: '1610000000001'
   status_code: 'OFD'
   phone: '9876543210'
   consignee: 'Priya Sharma'

2. WA.Expert automation:
   wa_phone = '+91' + '9876543210' = '+919876543210'

3. Branch on status_code:
   OFD -> Send OFD template to wa_phone:
          'Hi Priya! Your Delhivery shipment 161000001
           is out for delivery today. Please be available.'

   UD -> Send NDR template within 60 minutes:
         'Hi Priya, we tried delivering your order today but
          couldn\'t reach you. Tap to reschedule your delivery.'

   DL -> Send confirmation:
         'Your order has been delivered. How was your experience?'

Troubleshooting

Symptom	Likely cause	Fix
Webhook not firing	Webhook not registered or wrong URL	Log in to Delhivery Merchant Portal and confirm the webhook URL is saved. Ask your Delhivery account manager to send a test push.
WhatsApp not sending	Missing +91 prefix	Prepend +91 to the phone field from Delhivery before mapping to WA.Expert.
Phone field empty in payload	Phone not stored in shipment	Ensure the customer's phone was provided when creating the Delhivery shipment. Without it, the webhook has no phone to send.
Token API returning 401	Wrong auth format	Delhivery uses 'Token' not 'Bearer'. Header: Authorization: Token YOUR_TOKEN. Also include token as query param: ?token=YOUR_TOKEN.
Wrong template sent	Not branching on status_code	Use status_code (OFD, DL, UD, PKD) for branching, not the status text string which can vary slightly.
Works with Delhivery Express but not Surface	Same integration applies	The webhook format and status codes are identical across Delhivery Express, Surface, and Reverse services.

Common questions

Shiprocket or Delhivery direct?

Use this guide for a direct Delhivery merchant account. Use the Shiprocket guide if you ship through Shiprocket, which normalises events across multiple couriers into one webhook.

What auth does Delhivery use?

Token-based. Header: Authorization: Token YOUR_TOKEN (not Bearer). For the polling API, also pass as a query param: ?token=YOUR_TOKEN.

Why isn't the WhatsApp sending?

Most likely the bare phone number. Delhivery sends 9876543210. WA.Expert needs +919876543210. Prepend +91.

Key Delhivery status codes?

PKD/Manifested (dispatched), OFD (out for delivery), DL (delivered), UD (undelivered/NDR), RTO (return to origin). Branch on status_code.

What if phone is missing from payload?

Phone is only in the webhook if provided during shipment creation. Ensure your OMS passes the phone when creating Delhivery shipments.

Does this work for Delhivery reverse logistics?

Yes. Same status codes and webhook format across Express, Surface, and Reverse.

Connect Shiprocket to WhatsApp

Shiprocket: multi-courier normalised webhooks for 17+ couriers.

Read guide →

Connect WooCommerce to WhatsApp

Order and shipping notifications from WooCommerce stores.