Update Vehicle Details (Part B)

curl --request PUT \ --url https://api.sandbox.co.in/gst/compliance/e-way-bill/consignor/bill/{ewb_no}/vehicle \ --header 'Content-Type: application/json' \ --header 'authorization: <api-key>' \ --header 'x-api-key: <api-key>' \ --data ' { "ewbNo": 231010079649, "vehicleNo": "PQR1234", "fromPlace": "BANGALORE", "fromState": 29, "reasonCode": "1", "reasonRem": "vehicle broke down", "transDocNo": "1234", "transDocDate": "12/10/2017", "transMode": "1", "vehicleType": "R" } '

{ "code": 200, "data": { "alert": null, "data": { "validUpto": "18/05/2024 11:59:00 PM", "vehUpdDate": "13/05/2024 01:06:00 PM" }, "status": "1" }, "timestamp": 1763446641000, "transaction_id": "d96e4cc7-5dcd-4791-b43e-de87509a3d50" }

NIC validations

View NIC validations

Part-B can be updated by the generator of the e-way bill, if there is no transporter, or by the assigned transporter
Part-B can be updated only if the e-way bill is active, that is, not cancelled
Part-B can be updated only if the e-way bill is within validity period, that is, validity is not expired.
If vehicle is passed, the format of the vehicle number should be valid and as per the format
In case of road as a transportation mode , the vehicle number should be passed and transport document number is optional
In case of rail, air or ship as a transportation mode, the transport document number is must
Limiting generation of E Way Bill within 180 days of Document Date.
Railways integration for validating Trans Document NO .

Request body schema

View request body schema

Authorizations

authorization

string

header

required

E-Way Bill taxpayer access token returned by Authenticate.

x-api-key

string

header

required

Sandbox API key from your Sandbox account.

Headers

x-api-version

string

default:1.0.0

API version

x-source

enum<string>

default:primary

NIC server for the session used by this request. primary selects NIC1. secondary selects NIC2. Defaults to primary. See NIC1 and NIC2 routing.

Available options:

primary,

secondary

x-proxy

enum<string>

NIC server that receives the request. If omitted, the request goes to the server selected by x-source. When specified, selects the other server. See NIC1 and NIC2 routing.

Available options:

primary,

secondary

Path Parameters

ewb_no

string

required

Body

application/json

Request body for UpdateEWayBillVehicle.

ewbNo

number

required

Ewaybill Number

fromPlace

string

required

From Place

Maximum string length: 50

fromState

integer

required

From State

Required range: x <= 99

reasonCode

string

required

Reason Code

See vehicle update and consolidated-bill reasons.

Required string length: 1

reasonRem

string

required

Remarks

Maximum string length: 50

transMode

string

required

Transport Mode

See transport modes.

vehicleNo

string

Vehicle Number

See vehicle number formats.

Required string length: 7 - 15

vehicleType

string

Vehicle Type

See vehicle types.

transDocNo

string

Transport Document Number

Maximum string length: 15

transDocDate

string

Transport Document Date

Pattern: [0-3][0-9]/[0-1][0-9]/[2][0][1-2][0-9]

Response

200 - application/json

200 Part B updated / 726 Vehicle type can not be regular / 361 Invalid Vehicle Type

Option 1
Option 2

An E-Way Bill success or NIC business-failure response. Both variants use HTTP 200.

code

enum<integer>

required

NIC response code.

Available options:

200

timestamp

integer<int64>

required

Unix timestamp.

transaction_id

string

required

Request transaction identifier.

data

object

required

Show child attributes

Analytics

Compliance

Annexures

Update Vehicle Details (Part B)

NIC validations

Request body schema

View request body schema

Authorizations

Headers

Path Parameters

Body

Response

​NIC validations

​Request body schema

View request body schema

Authorizations

Headers

Path Parameters

Body

Response

NIC validations

Request body schema