Extend an E-Way Bill's validity

NIC computes an EWB's validity from distance at generation time — broadly 1 day per 100 km (1 day per 20 km for over-dimensional cargo). When the journey takes longer than that, you can ask NIC to extend the validity. The new window is computed by NIC based on remaining distance and consignment status — you don't pass hours.

When you can extend

NIC accepts extensions only inside a narrow window relative to validUpto:

• Before expiry: from 8 hours before validUpto until expiry.
• After expiry: up to 8 hours past validUpto.

Outside that window, NIC refuses the extension. An EWB that has been expired for a day cannot be revived — cancel it (if you're still inside the 24-hour cancel window) and generate a fresh one, or treat the rest of the journey as outside the EWB system if cancellation is also closed.

The call

POST /v1/ewaybills/extend HTTP/1.1
Host: api.in.onefinops.com
Authorization: Bearer eyJhbGciOi...
gstin: 29ABCDE1234F1Z5
Content-Type: application/json
X-Request-Id: 4f1d8a2c-…

{
  "ewbNumber": 112345678901,
  "vehicleNumber": "KA01AB1234",
  "fromPlace": "Hosur",
  "fromStateCode": "33",
  "fromPincode": 635109,
  "reasonCode": "4",
  "remark": "Transhipment at Hosur hub",
  "consignmentStatus": "M",
  "remainingDistance": 320,
  "transportMode": "1"
}

reasonCode:

consignmentStatus:

transitType (only when consignmentStatus is T):

remainingDistance is the kilometres still to go from your current location to the destination. NIC uses this to compute the new validUpto.

Response

The EWB record with the updated validUpto. The vehicle and consignment details are otherwise unchanged.

Where to next

• Update Part-B — if the vehicle has also changed.
• Cancel an E-Way Bill — when extension isn't possible.
• Generate an EWB — back to the lifecycle.