Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Integration guide

How to Connect Delhivery to Apragya: Token, Pickup and First Booking

For e-commerce and dispatch teams: what to collect from Delhivery, where it goes, and how to prove booking, labels and tracking work before the busy season.

A founder packing a block-printed kurta into a mailer bag

To connect Delhivery to Apragya you need an API token, the client name registered with Delhivery, a registered pickup location and a webhook secret. Delhivery's API authenticates with the token on every call.

The client name matters more than it looks. It identifies the pickup account, and a booking without it is rejected by the courier with an unhelpful message, so Apragya checks it first.

Below are the steps, an illustrative example from Jaipur and a short list of first-week checks.

How to connect Delhivery to Apragya

Get the API token and the registered client name from Delhivery, and confirm your pickup location is registered with them. Agree a webhook secret for tracking callbacks.

In Apragya, add a Delhivery connection with the client name and pickup location as settings, and the token and secret as credentials. Run the test, then book, label and cancel a test parcel before going live.

  1. Collect the API token and client name from Delhivery.
  2. Confirm the pickup location is registered.
  3. Add the Delhivery connection in Apragya.
  4. Enter the webhook secret agreed with Delhivery.
  5. Test, then book, label and cancel one parcel.

What slows a Delhivery setup down

Wrong token

A token from a test account used on the live account.

Client name mismatch

The name differs from the one Delhivery registered.

Pickup not registered

Bookings for an address the courier does not collect from.

Unsigned callbacks

Scans refused because no secret was shared.

An example: a Jaipur block-print apparel brand

Take an illustrative D2C brand preparing for the festive season. The founder wanted labels printing from the packing table and tracking visible to support before orders peaked.

Five days from token to festive-ready

  1. Day 1

    API token and client name received from Delhivery.
  2. Day 2

    Connection added with the pickup location.
  3. Day 3

    Test passed; pincodes and rates checked.
  4. Day 4

    Ten test bookings with labels and a pickup.
  5. Day 5

    Signed scans arriving on the timelines.
Day four was the real test: labels, pickup and a cancellation, all from Apragya.

By the first festive weekend, packing staff printed labels at the table, the afternoon pickup was scheduled from the dispatch, and support read scan history on the shipment without opening the courier panel.

A courier lifting a crate of mailer bags while a packer holds a sheet
Day four's ten test parcels left on a pickup booked from the dispatch.

How the Delhivery API token and settings are used

Step 1 of 5

Token

The API token is stored encrypted and sent on every call.

  1. Token: The API token is stored encrypted and sent on every call.
  2. Client name and pickup: Saved on the connection and checked before each booking.
  3. Test: A light read proves the token works without booking anything.
  4. Labels and pickups: Fetch labels and schedule pickups for booked shipments.
  5. Callbacks: Scans are accepted only when their signature matches the secret.

Delhivery client name setup and webhooks, compared

The setup has two halves. The outbound half, token and client name, lets you book. The inbound half, the webhook secret, lets scans arrive on their own. Skipping the second half leaves you with manual re-syncs.

Half set up, against fully set up

FeatureToken onlyApragya fully set up
BookingWorks if client name is rightChecked before each call
Labels and pickupWorksWorks
ScansManual re-sync onlyArrive on signed callbacks
Support viewStale until re-syncedCurrent timeline

Checked against public information on 16 September 2026.

Why the Delhivery webhook setup is worth finishing

Current status

Scans arrive as the courier sends them.

Correct order

A late scan cannot undo a delivered status.

Disputes settled

The courier's own text is kept beside our status.

One shipment record

Order, delivery note and label linked.

Agents with review

Stuck parcels can be flagged for a person.

More couriers

Blue Dart and Shiprocket follow the same pattern.

Read the Delhivery integration overview and pick lists.

First-week checks

  1. Book parcels to metro and remote pincodes.
  2. Print labels from the packing table.
  3. Schedule and confirm one pickup.
  4. Cancel one test booking.
  5. Confirm scans arrive without a manual re-sync.

Run these a week before your busy season, not during it.

What it costs to start

INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus Inventory and Warehousing
2,000
AI Credits a month
Included on Starter
Free
Up to 3 users
CRM, HR and Vendor Onboarding

Connecting Delhivery, answered

Where is the API token?
Delhivery provides it for your account; ask your Delhivery contact if it is not visible to you.
What exactly is the client name?
The name Delhivery registered for your pickup account. It must match exactly.
Does the test book a parcel?
No. It makes a light read that only proves the token works.
Why are scans not arriving?
Check the webhook secret with Delhivery, then re-sync the shipment by hand.
What does it cost to start?
Inventory and Warehousing is available from the Starter plan, INR 3,999 a month for up to 10 users, which includes CRM and HR plus a choice of enterprise apps and 2,000 AI Credits a month. Pro, at INR 7,999 a month, covers 25 users and every enterprise app.

Be festive-ready a week early

Add the Delhivery connection, book ten test parcels and watch the scans arrive.