Delhivery configuration

The current Delhivery constructor accepts:

new DelhiveryClient({
  token: "your-token",
  clientName: "your-client-name",
  baseUrl: "https://track.delhivery.com", // optional
});

OpenLogistics({ provider: "delhivery", token, clientName, baseUrl }) accepts the same options and is the recommended entry point.

Option	Type	Required	Notes
token	string	yes	Static Delhivery API token
clientName	string	yes	Registered Delhivery client name
baseUrl	string	no	Overrides the built-in API host

What is configurable

• API token
• Registered client name
• Base URL override for staging or production

Exposed methods

• createOrder()
• updateOrder()
• cancelOrder()
• generateLabel()
• createPickupRequest()
• trackByWaybill()
• trackByOrderId()
• trackByWaybills()
• checkServiceability()
• calculateRate()
• fetchWaybill()
• fetchWaybills()

Practical guidance

• Use createOrder() for B2C manifestation
• Use checkServiceability() before creating orders
• Use generateLabel() for packing slip generation
• Use createPickupRequest() for pickup scheduling
• Set baseUrl explicitly when you need a non-default Delhivery environment