If you have a business account with Delhivery, you can connect it to Mercayo directly, beside Shiprocket or Shipway or instead of them. Labels, pickups and tracking then run through your own Delhivery account, at your Delhivery rates, and the COD money goes to your Delhivery account as before. Seeing the card needs the right to see orders; connecting or disconnecting needs the right to change settings.
Before You Start
- Your API token: in Delhivery One, Settings › API Setup. Use the live token, not the test one.
- Your warehouse must already be registered with Delhivery (Delhivery One › Settings › Pickup Locations). You type its name exactly as Delhivery shows it: that is how Delhivery knows where to collect from.
- The warehouse's address, PIN code and a phone number.
Connect It
- Open Settings › Couriers and scroll to Direct Courier Accounts.
- On the Delhivery card, fill in API Token, Account Name (as Delhivery shows it, so your team knows the account) and the Pickup Address: Warehouse Name at Delhivery, Phone, Address, City, State and PIN Code.
- Press CONNECT DELHIVERY. The button shows "Connecting to Delhivery…" at once. Delhivery checks the token; if it refuses, nothing is saved and the card says why.
- Right after the first connect, a panel shows an address and a secret, once. Send both to your Delhivery account manager or support and ask them to send status updates to the address, with the secret in a header named x-api-key. Press DONE, I HAVE SENT IT. Until they do, Mercayo asks Delhivery about quiet parcels every 12 hours.
The token is kept encrypted and never shown again. The first account you connect becomes the Default one labels use.
What the Card Shows
| Fact | What It Shows |
|---|---|
| Account | The account name you typed. |
| Connected | When it was connected. |
| Pickup Addresses | Your Delhivery warehouses Mercayo knows, with city and PIN code. |
| Status Updates Address | The address Delhivery sends updates to, with COPY. |
Under them, Through Mercayo lists each call and whether it is Ready or Live Check Pending:
| Call | Delhivery |
|---|---|
| Labels and AWBs | Ready |
| Pickup requests | Ready: one per warehouse and day; more parcels the same day join it |
| Cancelling a parcel | Ready, until Delhivery collects it |
| Answers to failed deliveries | Live Check Pending: answer in Delhivery One meanwhile |
| Return pickups | Live Check Pending: book them in Delhivery One meanwhile |
| Adding a pickup address | Ready: registered at Delhivery too |
Live Check Pending means Mercayo built the call from Delhivery's public material but has not yet seen it work on a real merchant account, so it is refused on real accounts until Mercayo checks it with a merchant. Nothing wrong ever reaches Delhivery.
Making Labels
With Delhivery as your default (or chosen when you press GENERATE LABELS), each parcel:
- is checked against the PIN code (served at all, and for COD on a cash order);
- gets Delhivery Surface or Delhivery Air by your Courier Rules, at the prices your Delhivery account gives (and Delhivery's days);
- is booked with your warehouse as the pickup, and gets its AWB and Delhivery's sort code at once;
- gets Delhivery's own label (its packing slip) and your branded label, with the sort code printed.
A part-paid cash order tells Delhivery to collect only the amount still due; the order's full value goes as its worth.
Questions
Can I use Delhivery and Shiprocket together? Yes. Labels use your default account; you can pick the other when you generate labels, and each parcel stays with the account that booked it.
Delhivery said my token is wrong. Copy it again from Delhivery One › Settings › API Setup, the live one. A token from Delhivery's test system does not work on real parcels.
My warehouse is not found. The name must match Delhivery's exactly, including spaces. Add more warehouses with ADD PICKUP ADDRESS under Labels and Pickups; Mercayo registers them at Delhivery too.