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

How to Connect BlueDart to Apragya and Start Tracking Shipments

For dispatch managers and IT admins: the details to collect, the order to enter them, and the checks that prove bookings and tracking will work.

An operations head weighing a parcel at a hosiery dispatch counter

To connect BlueDart to Apragya you need three account details from Blue Dart, a registered pickup address and a shared secret for tracking callbacks. With those ready, the setup takes a short session.

The connector checks what it can before calling Blue Dart. A missing licence key or pickup location is reported plainly, instead of as a confusing rejection from the courier.

Below are the steps, an illustrative example from Ludhiana and the checks to run before you move all dispatches.

How to connect BlueDart to Apragya

Ask Blue Dart for API access on your account. You need the customer code, a licence key and a login ID, and your registered pickup address. Agree a webhook secret so tracking callbacks can be signed.

In Apragya, add a Blue Dart connection: put the customer code and pickup location in the settings, and the licence key, login ID and secret in the credentials. Run the test, then book a test parcel.

  1. Request API access from Blue Dart for your customer code.
  2. Note the licence key, login ID and pickup address.
  3. Add the Blue Dart connection in Apragya.
  4. Enter the webhook secret shared with Blue Dart.
  5. Run the test and book one test parcel.

An example: a Ludhiana hosiery exporter

Take an illustrative exporter that ships sample parcels to buyers across India by Blue Dart. The operations head set up the connection on a Friday and wanted to book the next Monday.

The connection details, as entered

Blue Dart connection

  1. Every request is refused without it.

  2. Issued by Blue Dart for API use.

  3. Needed together with the licence key.

  4. The registered collection address.

  5. Used to verify tracking callbacks.

  6. A known pincode returned as served.

With all six in place, Monday's first booking went through on the first try.

On Monday the team booked eight sample parcels. Scans started arriving that afternoon, and the operations head read the first delivered status on the shipment record two days later.

Eight wrapped parcels on a bench with the first one wearing a rosette
Eight test parcels went out on Monday, and the first delivered scan arrived two days later.

Common reasons a courier setup stalls

Half the credentials

A licence key without the login ID, or the reverse.

No pickup address

Bookings are refused because nobody set the collection point.

No callback secret

Tracking callbacks are refused because they cannot be verified.

Untested pincodes

Orders are promised to places the courier does not serve.

How the Blue Dart licence key setup fits together

Step 1 of 5

Account detail

The customer code goes on the connection's settings.

  1. Account detail: The customer code goes on the connection's settings.
  2. Secrets: The licence key, login ID and webhook secret are stored encrypted.
  3. Test: The test checks a known pincode, which proves the credentials work.
  4. Booking checks: Booking stops early if a credential or pickup address is missing.
  5. Callbacks: Each tracking callback is verified against the secret before use.

Setting up the BlueDart tracking webhook

Tracking can come from callbacks or from a manual re-sync. Callbacks are better, because scans arrive as they happen. They are also the part that needs care: an unverified callback could mark any parcel delivered, so Apragya refuses callbacks it cannot verify.

Callback set-up, compared

FeatureWithout a secretApragya with a secret
Callbacks acceptedNo, refusedYes, when the signature matches
Scan timingOnly on manual re-syncAs the courier sends them
Fake delivered statusNot possible, refusedNot possible, verified
Raw courier textNot receivedKept beside our status

Checked against public information on 16 September 2026.

Before you move every dispatch

  1. Book a few test parcels to different regions.
  2. Confirm scans arrive on the shipment timeline.
  3. Try a cancellation on a test booking.
  4. Show support where to read the timeline.

If scans do not arrive, check the secret first, then use a manual re-sync on the shipment.

What you get once BlueDart API credentials are in

Shipments with AWB

Carrier, waybill, weight and freight on the shipment.

Status in one vocabulary

Blue Dart codes mapped to one set of statuses.

Scans in order

A late scan cannot overwrite a delivered status.

Linked documents

Delivery notes and packing slips on the same shipment.

Agents with review

An agent can flag parcels that have stopped moving.

Access by role

Dispatch and support see what they need.

Read the BlueDart integration overview and shipments.

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 BlueDart, answered

Where do we get the licence key?
From your Blue Dart account team, who issue API access for your customer code.
Why are our callbacks being refused?
Usually the secret is missing or differs from the one Blue Dart signs with.
Can we test without booking a parcel?
Yes. The connection test checks pincode service, which needs valid credentials.
Can we connect more than one pickup address?
Add a connection per registered pickup location if your dispatch runs from several sites.
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.

Book Monday's parcels from Apragya

Gather the Blue Dart details, add the connection and run the pincode test.